[SPY-91] optimized operations are not being rescheduled correctly when receiving NOT_MY_VBUCKET responses Created: 02/Jul/12 Updated: 29/May/13 |
|
| Status: | Open |
| Project: | Spymemcached Java Client |
| Component/s: | None |
| Affects Version/s: | 2.7.2, 2.7.3, 2.8.0, 2.8.1 |
| Fix Version/s: | .next |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Michael Nitschinger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When a NOT_MY_VBUCKET response is received in the middle of an optimized operation, the current retry logic will unqueue the optimized operation and retry it rather than retry just the contained operation. This causes operation failures during rebalance activities.
|
| Comments |
| Comment by Matt Ingenthron [ 02/Jul/12 ] |
| I have an integrationey/unit test which reproduces this issue, along with a proposed fix which is a work in progress. The test is on the Couchbase Java Client, but the fix is actually here at the lower levels of SPY. |
| Comment by Matt Ingenthron [ 11/Jan/13 ] |
| This is related to re-enabling optimization. |