Details
Bug
Closed
Major
Description
The current Python client cannot handle topology changes dynamically. It should learn to do so in one of two ways.
1) Implement handling of fast-forward map.
2) Implement retry of nodes.
When a node is added to the cluster and rebalance is started, a new map is published with a fast-forward section and an updated node list with the new node listed.
The python client should handle not-my-vbucket errors by trying the fast forward map, or should retry each node (maybe twice?) until some node takes the item.
1) Implement handling of fast-forward map.
2) Implement retry of nodes.
When a node is added to the cluster and rebalance is started, a new map is published with a fast-forward section and an updated node list with the new node listed.
The python client should handle not-my-vbucket errors by trying the fast forward map, or should retry each node (maybe twice?) until some node takes the item.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Gerrit Reviews
Matt Ingenthron
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.0 Beta [ 10214 ] | |
| Component/s | library [ 10118 ] |
Farshid Ghods
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Benjamin Young
made changes -
| Fix Version/s | 0.7 [ 10213 ] | |
| Fix Version/s | 1.0 Beta [ 10214 ] |
Mark Nunberg
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |