Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
5.5.0
-
Triaged
-
Yes
Description
Following rebalance exit observed in 5.5.0-2915 eventing component level test:
Rebalance exited with reason {service_rebalance_failed,eventing,
|
{linked_process_died,<21491.27678.77>,
|
{timeout,
|
{gen_server,call,
|
[<21491.8799.0>,
|
{call,"ServiceAPI.GetCurrentTopology",
|
#Fun<json_rpc_connection.0.125340786>},
|
60000]}}}}
|
All the subsequent rebalances seem to be failing with the following error:
Rebalance exited with reason
{badmatch,failed}This seems to be same as MB-29121 - but filing this as that bug is old and closed
Supportal: https://supportal.couchbase.com/snapshot/59e5206c538c3721ce5eb2c5ecd627e3::0
More logs:
https://s3.amazonaws.com/bugdb/jira/collectinfo-2018-06-19T235941-ns_1%40172.23.104.16.zip
https://s3.amazonaws.com//bugdb/jira/collectinfo-2018-06-19T235941-ns_1%40172.23.104.18.zip
Cluster: http://172.23.104.16:8091/ui/index.html#!/logs/collectInfo/result
Attachments
Issue Links
- causes
-
MB-30184 Rebalance is not progressing, autofailover eventing node at 100% CPU
- Closed