http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/CCBC-91 Couchbase C client library libcouchbase scenario: <br/> 1. Start PHP client in a loop setting and getting against a 2 node cluster <br/> 2. Click failover to kick a node out, click rebalance to make it unassociated <br/> 3. Walk through the setup wizard on that node, re-add it to the cluster <br/> 4. After adding, click rebalance <br/> <br/> Expected behavior: <br/> During rebalance in step 4, which is an add node scenario, no timeouts are expected. <br/> <br/> Observed behavior: <br/> During rebalance in step 4, I see timeouts from PHP, and they continue even after the rebalance has completed. PHP 5.3.3 (cli) (built: Jun 27 2012 12:25:48) <br/> libcouchbase1-1.0.4-1 <br/> CentOS release 5.8 (Final), x86_64 <br/> Couchbase Server 1.8.1 Enterprise CCBC-91

timeouts seen after failover, rebalance and add back

Bug Blocker Closed Fixed Public Sergey Avseyev Matt Ingenthron Mon, 13 Aug 2012 05:13:19 -0500 Tue, 13 Nov 2012 04:21:35 -0600 Sat, 18 Aug 2012 05:35:45 -0500 1.0.4 1.0.5 0 1 A packet capture of this same issue, with the client on MacOS X and CentOS 5.8 servers with Couchbase Server 1.8.1 enterprise edition may be found at <a href="http://dl.dropbox.com/u/1537838/failover-maybe-issue">http://dl.dropbox.com/u/1537838/failover-maybe-issue</a> <a href="http://review.couchbase.org/19563">http://review.couchbase.org/19563</a> Note from discussion, this is a possible fix, not sure. Sergey and I reproduced the issue, and it&#39;s related to the series of steps outlined above. The underlying libcouchbase is not receiving the updated configuration for some reason, and thus is sending items to the wrong node, and then they&#39;re timing out. <br/> <br/> Sergey will do more work on finding the specific cause. The patch <a href="http://review.couchbase.org/19599">http://review.couchbase.org/19599</a> and aforementioned <a href="http://review.couchbase.org/19563">http://review.couchbase.org/19563</a> solves the issue. <br/> <br/> To reproduce it for sure you should failover the node is currently used by client to listen config changes. (Usually it is the first successfull node from initial node list) Rank 10168 Time In Status