[PYCBC-33] Many operations are timing out during rebalancing Created: 18/May/12 Updated: 11/May/13 Resolved: 11/May/13 |
|
| Status: | Closed |
| Project: | Couchbase Python Client Library |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 0.10.0 |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | wenxiang | Assignee: | Mark Nunberg |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Couchbase 1.8.0 Community
Ubuntu 12.04 Server Cluster of 3 servers, 8GB ram each Linux RAID 10, 4 x WD RE4 drives |
||
| Description |
|
I tried adding a fourth server with similar specs to the cluster, and found that during the rebalancing, a large number of operations simply timed out after about 30 secs.
The same behavior was observed using the VBucketAware Python client, local Moxi servers and telnetting directly to the CB servers. I was under the impression that if the client/Moxi hits a wrong server during rebalancing it's supposed to immediately return a "not my vbucket" error so it can immediately figure out the actual server to query? |
| Comments |
| Comment by Mark Nunberg [ 11/May/13 ] |
| handled by LCB |