Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.10.0
-
Component/s: None
-
Security Level: Public
-
Labels:None
-
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?
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?
Activity
Mike Wiederhold
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Project | Couchbase Server [ 10010 ] | Couchbase Python Client Library [ 10050 ] |
| Key | MB-5330 |
|
| Affects Version/s | 1.8.0 [ 10248 ] |
Matt Ingenthron
made changes -
| Assignee | Matt Ingenthron [ ingenthr ] |
Matt Ingenthron
made changes -
| Assignee | Matt Ingenthron [ ingenthr ] | Mark Nunberg [ mnunberg ] |
Mark Nunberg
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | 0.10.0 [ 10607 ] | |
| Resolution | Fixed [ 1 ] |