Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
4.6.0
-
Untriaged
-
Unknown
Description
I believe this has come up previously so it might already be fixed in 5.x but I was unable to verify that myself.
I have an automated cluster setup which failed to rebalance and is not correctly exposing its services (i.e., clients can't get the N1QL service information).
A couple questions:
1 - Why did the rebalance fail?:
The UI logs show:
Rebalance exited with reason {pre_rebalance_config_synchronization_failed,
[{'ns_1@ec2-52-37-57-66.us-west-2.compute.amazonaws.com',
down}]}
2 - Why isn't the rebalance marked as failed in the UI?
The UI shows the "Rebalance" button as active (see screenshot)
3 - Even though the query nodes are part of the cluster, why are they not exposing themselves as part of the configuration?
Logs are at:
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-34-213-233-134.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-34-213-239-32.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-35-162-143-111.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-35-166-64-240.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-52-37-57-66.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-52-42-121-36.us-west-2.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/rebalance_failure/collectinfo-2017-09-12T150258-ns_1%40ec2-54-186-109-121.us-west-2.compute.amazonaws.com.zip