Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
Security Level: Public
-
None
Description
Since the OperationState is accessed by multiple threads, there can be a coherency issue if the application code is trying to reference the OperationState after an OperationFuture has completed, but a previous value of the OperationState is not seen on the thread of the application blocking on that OperationFuture.
Attachments
For Gerrit Dashboard: SPY-88 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
16251,3 | Retry not my vbucket error for optimized sets. SPY-88 | master | spymemcached | Status: MERGED | +2 | +1 |
16255,4 | Make the OperationState volatile. SPY-88 | master | spymemcached | Status: MERGED | +2 | +1 |
17027,2 | JCBC-52: Fix StringUtils.join() | master | spymemcached | Status: MERGED | +2 | +1 |
18670,4 | Disable optimization by default, remove assert. SPY-88. | master | spymemcached | Status: MERGED | +2 | +1 |