Loading...

XML

Word

Printable

Triage:
Untriaged
Operating System:
Centos 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump:

Hide
https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.155.zip
https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.211.zip
https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.212.zip
https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.213.zip

Show
https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.155.zip https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.211.zip https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.212.zip https://cb-engineering.s3.amazonaws.com/node_down_post_reboot/collectinfo-2021-03-10T121420-ns_1%40172.23.105.213.zip
Story Points:
1
Is this a Regression?:
Unknown

Build: 7.0.0-4629

Scenario (Test for auto_retry_of_failed_rebalance):

3 node cluster, couchbase bucket (replica=2)
Add 1 more kv node and start rebalance
During rebalance, reboot one of the existing cluster node (172.23.105.211) so that the rebalance fails

Observation:

Post reboot, node '211' is stuck in warmup condition and sdk reconnect attempts fails with "ConnectTimeoutException"

No reviews matched the request. Check your Options in the drop-down menu of this sections header.

There are no open Gerrit changes

Node stuck in warm up after reboot during rebalance