Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.5.0
-
Untriaged
-
Unknown
Description
Build 6.5.0-3633
In high bucket density test(with 30 buckets), if we hard fail over kv node and start rebalance it fails with following error-
Rebalance exited with reason {service_rebalance_failed,fts,
|
{linked_process_died,<0.351.348>,
|
{timeout,
|
{gen_server,call,
|
[<0.4725.0>,
|
{call,"ServiceAPI.GetCurrentTopology",
|
#Fun<json_rpc_connection.0.102434519>},
|
60000]}}}}.
|
Rebalance Operation Id = 1656f7043dba1e707c7c243547336652
|
|
Logs:
Data nodes-
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.12.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.13.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.15.zip
Other nodes-
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.96.20.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.96.23.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.177.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.19.zip
https://s3.amazonaws.com/bugdb/jira/failover_reb_fail/collectinfo-2019-07-04T135349-ns_1%40172.23.97.20.zip