Details
-
Task
-
Resolution: Fixed
-
Major
-
4.6.0
Description
A vbucket's max_cas can be "poisoned" by a node with a future clock, this can only be undone by waiting for time to pass or changing a nodes real clock, neither may be desirable if the future clock was a big mistake (think time -s "3016 3-Oct 14:14")
So update epctl so that the damage can be undone to some extent, another tool for the toolbox...
Attachments
For Gerrit Dashboard: MB-21190 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
68517,8 | MB-21190: cbepctl support to change max_cas | watson | ep-engine | Status: MERGED | +2 | +1 |
68736,2 | MB-21190: cbepctl support to change max_cas | watson | ep-engine | Status: MERGED | +2 | +1 |
68754,1 | Merge remote-tracking branch 'couchbase/watson' | master | ep-engine | Status: MERGED | +2 | +1 |
68810,2 | Merge remote-tracking branch 'couchbase/watson' | master | ep-engine | Status: MERGED | +2 | +1 |
68994,5 | MB-21190: update log message for set max_cas | watson | ep-engine | Status: MERGED | +2 | +1 |
69787,1 | Merge remote-tracking branch 'couchbase/watson' | master | ep-engine | Status: MERGED | +2 | +1 |