Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.6.0
-
None
-
Untriaged
-
0
-
Unknown
Description
set/add 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 offers two modes of protection to prevent the above
- Error - If the input CAS exceeds the current wall clock time by a configured threshold,KV rejects the operation and an error is returned.
- Replace - In this mode KV accepts the operation but the CAS is regenerated.
Currently if the protection is set to replace mode, CAS in the response for Add/Set with meta is set to the input provided (poisoned CAS) instead of the newly generated CAS.
Attachments
Issue Links
- relates to
-
MB-61385 Limit vbucket "max_cas"
-
- In Progress
-
For Gerrit Dashboard: MB-62248 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
212738,5 | MB-62248: Return regenerated CAS to client | master | kv_engine | Status: MERGED | +2 | +1 |