Details
-
Bug
-
Resolution: Not a Bug
-
Critical
-
7.2.0, 7.2.3
-
Operating System : Microsoft Windows Server 2019 Base
AMI ID : ami-093693792d26e4373
Couchbase Enterprise Edition build 7.2.0-5325
-
Untriaged
-
Windows 64-bit
-
-
0
-
Unknown
Description
Steps to reproduce
- Launched Microsoft Windows Server 2019 Core Base EC2 instances with AMI : ami-00c6f475579da3efa
- Installed Couchbase Enterprise Edition build 7.2.0-5325 on the nodes
- Created a single node cluster with ec2-18-207-3-113.compute-1.amazonaws.com. Configured all services on the node
- Added node ec2-54-237-99-59.compute-1.amazonaws.com onto the cluster with all services
- Rebalance fails. Retry of the rebalance consistently produces the same failure
Rebalance exited with reason {service_rebalance_failed,backup,
|
{worker_died,
|
{'EXIT',<0.18645.0>, |
{rebalance_failed,
|
{service_error,
|
<<"could not add node '4db358c6c32e9c5b91aeaa9b03c67e06': exhausted retry count after 5 attempts: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 172.31.38.59:9124: i/o timeout\"">>}}}}}. |
Rebalance Operation Id = eeaee5127b5d28970da7c66d919581dd
|
Also observing similar behavior with Microsoft Windows Server 2019 Base EC2 instances with AMI : ami-093693792d26e4373