[PYCBC-4] cannot handle topology changes Created: 22/Aug/11 Updated: 11/May/13 Resolved: 29/Sep/11 |
|
| Status: | Closed |
| Project: | Couchbase Python Client Library |
| Component/s: | library |
| Affects Version/s: | None |
| Fix Version/s: | 0.7 |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Farshid Ghods |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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. |
| Comments |
| Comment by Farshid Ghods [ 29/Sep/11 ] |
| https://github.com/couchbase/couchbase-python-client/commit/3f315ec8c6ea73ef03f49f5b0f79ddcd9389ad19 |