Details
Description
Rebalance fails with backup service and Address Family is set to IPv4-only.
Steps to reproduce:
- Create a 1 node cluster(.219) with data service
- Set the address family to ipv4-only
- Add a 2nd node(.237) with backup service
- Rebalance
Result: Rebalance fails
The following message pops up: Rebalance failed. See logs for detailed reason. You can try again.
We see the following message in the logs:
Service 'backup' exited with status 1. Restarting. Messages:
2022-11-01T21:36:26.620-07:00 INFO (Main) Initialized logger {"log level": "debug"}
2022-11-01T21:36:26.620-07:00 INFO (Main) Getting credentials
2022-11-01T21:36:26.620-07:00 DEBUG (Main) File limit info {"curr": 200000, "max": 200000, "err": null}
2022-11-01T21:36:26.620-07:00 DEBUG (REST) (Attempt 1) (GET) Dispatching request to 'http://localhost:8091/pools/default/nodeServices'
2022-11-01T21:36:26.621-07:00 ERROR (REST) (Attempt 1) (GET) Failed to perform request to 'http://localhost:8091/pools/default/nodeServices': Get "http://localhost:8091/pools/default/nodeServices": dial tcp [::1]:8091: connect: connection refused
2022-11-01T21:36:26.622-07:00 WARN (REST) failed to bootstrap client, will retry: failed to execute request: Get "http://localhost:8091/pools/default/nodeServices": dial tcp [::1]:8091: connect: connection refused
2022-11-01T21:36:26.622-07:00 ERROR (Main) Failed to run node {"err": "could not create REST client: failed to bootstrap client: failed to connect to any host(s) from the connection string, check username and password"}
Have attached the rebalance report and the logs.
Note: the rebalance eventually gets completed but the message "Rebalance failed. See logs for detailed reason. You can try again." keeps popping from time to time.
The rebalance fails only when the Address Family is set to IPv4-only.
It can also be noted that in case the first node(.219) has the backup service and the second node(.237) has the data service, then the rebalance completes without any issues.
Attachments
Issue Links
- links to