Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.6.0
-
None
-
Untriaged
-
0
-
Unknown
-
March-June 24
Description
set/del with meta can update the CAS of a vbucket to any value - a faulty input can "poison" the max_cas of the vbucket - affecting the hybrid logical clock logic (and impacting LWW XDCR).
KV should add a configurable limit on how far in the future from the local clock a CAS value can be.
This would introduce a new error path for set/del meta which XDCR may need to handle Neil Huang
Attachments
Issue Links
For Gerrit Dashboard: MB-61385 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
208246,4 | MB-61385: Introduce MaxFutureCasThreshold in HLCT | master | kv_engine | Status: MERGED | +2 | +1 |
208810,14 | MB-61385: Handle invalid CAS values | master | kv_engine | Status: MERGED | +2 | +1 |
208921,1 | MB-61385: Validate CAS before set/del with meta command | master | kv_engine | Status: ABANDONED | 0 | +1 |
209197,10 | MB-61385: Add counter to track the number of invalid CAS values | master | kv_engine | Status: MERGED | +2 | +1 |