Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.1.6
-
Fix Version/s: 1.2 Beta-2
-
Component/s: None
-
Labels:None
Description
Happens during the rebalancing-out of two nodes.
Reproduce:
* Perform get/set operations continuously
* Rebalance out two nodes
poof!
I was using multiple client handles for this test.. it seems each of them got that error.
Reproduce:
* Perform get/set operations continuously
* Rebalance out two nodes
poof!
I was using multiple client handles for this test.. it seems each of them got that error.
Activity
Mark Nunberg
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Affects Version/s | 1.1.6 [ 10337 ] |
Matt Ingenthron
made changes -
| Fix Version/s | 1.1.7 [ 10341 ] | |
| Fix Version/s | 1.2 [ 10298 ] |
John Zablocki
made changes -
| Fix Version/s | 1.2 Beta-2 [ 10397 ] | |
| Fix Version/s | 1.2 [ 10298 ] |
Matt Ingenthron
made changes -
| Priority | Major [ 3 ] | Blocker [ 1 ] |
John Zablocki
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
John Zablocki
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
John Zablocki
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
John Zablocki
made changes -
| Fix Version/s | 1.1.7 [ 10341 ] |
Just wondering if major is the right priority for this issue given that this happens during rebalancing
Do users tend to ignore one or two errors and are okay with retries for these type of errors