Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.2
-
Fix Version/s: 1.0.4
-
Component/s: library
-
Security Level: Public
-
Labels:
-
Environment:Centos5x OR Ubuntu 11x running Couchbase 1.8.0. 3 Node Cluster, plenty of available RAM and DISK. PHP 5.3. libcouchbase version 1.0.3-1
Description
This bug is reported by a customer. Whenever they issue a rebalance(after removing a node from the cluster or add a new node), client operations(PHP - sample code attached) time out with the error below
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n>
This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors.
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n>
This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors.
Activity
Hari Subramaniam
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
This bug is reported on behalf of a brand new paid-customer (SocialPoint - Spain). Whenever they issue a rebalance(after removing a node from the cluster or add a new node), client operations(PHP - sample code attached) time out with the error below
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n> This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors. IMPACT: Customer considers this a BLOCKER for rolling out their new game. About 28k revenue is in jeopardy pending a resolution to this issue. Support Case# 1156 (http://support.couchbase.com/tickets/1156) EXPECTATION: A workaround or configuration change to alleviate the cluster un-responsiveness OR FIX to the PHP code. |
This bug is reported by a customer. Whenever they issue a rebalance(after removing a node from the cluster or add a new node), client operations(PHP - sample code attached) time out with the error below
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n> This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors. IMPACT: Customer considers this a BLOCKER for rolling out their new game. About 28k revenue is in jeopardy pending a resolution to this issue. Support Case# 1156 (http://support.couchbase.com/tickets/1156) EXPECTATION: A workaround or configuration change to alleviate the cluster un-responsiveness OR FIX to the PHP code. |
Matt Ingenthron
made changes -
| Assignee | Jan Lehnardt [ jan ] | Hari Subramaniam [ hari ] |
Matt Ingenthron
made changes -
| Description |
This bug is reported by a customer. Whenever they issue a rebalance(after removing a node from the cluster or add a new node), client operations(PHP - sample code attached) time out with the error below
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n> This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors. IMPACT: Customer considers this a BLOCKER for rolling out their new game. About 28k revenue is in jeopardy pending a resolution to this issue. Support Case# 1156 (http://support.couchbase.com/tickets/1156) EXPECTATION: A workaround or configuration change to alleviate the cluster un-responsiveness OR FIX to the PHP code. |
This bug is reported by a customer. Whenever they issue a rebalance(after removing a node from the cluster or add a new node), client operations(PHP - sample code attached) time out with the error below
PHP Warning: Couchbase::set(): Failed to store a value to server: Operation timed out in /root/test_worker.php on line <n> This issue is consistent for both the customer as well as our in-house reproduction in Support. There are no errors on the server side. Rebalance does complete. And once rebalance is complete, the same script runs fine without any errors. |
Hari Subramaniam
made changes -
| Assignee | Hari Subramaniam [ hari ] | Matt Ingenthron [ ingenthr ] |
Hari Subramaniam
made changes -
| Environment | Centos running Couchbase 1.8.0. 3 Node Cluster, plenty of available RAM and DISK. PHP 5.3 | Centos5x OR Ubuntu 11x running Couchbase 1.8.0. 3 Node Cluster, plenty of available RAM and DISK. PHP 5.3. libcouchbase version 1.0.3-1 |
Matt Ingenthron
made changes -
| Assignee | Matt Ingenthron [ ingenthr ] | Sergey Avseyev [ avsej ] |
Sergey Avseyev
made changes -
| Attachment | report.pdf [ 13105 ] |
Sergey Avseyev
made changes -
| Project | Couchbase PHP client library [ 10049 ] | Couchbase C client library libcouchbase [ 10070 ] |
| Key | PCBC-64 |
|
| Affects Version/s | 1.0.2 [ 10284 ] | |
| Affects Version/s | 1.0.2 [ 10310 ] | |
| Component/s | library [ 10110 ] | |
| Component/s | library [ 10134 ] |
Sergey Avseyev
made changes -
| Assignee | Sergey Avseyev [ avsej ] | Jan Lehnardt [ jan ] |
Sergey Avseyev
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 1.0.4 [ 10327 ] | |
| Resolution | Fixed [ 1 ] |
Sergey Avseyev
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
libcouchbase version installed?
CentOS Version?
Also needed is a description of what kind of rebalance is happening here. A "failover" click followed by a "rebalance" is different than a "remove node" followed by a "rebalance". Please outline the specific steps you'd used to reproduce.