Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
6.0.0
-
None
-
6.0.0-1494
-
Untriaged
-
Unknown
Description
Script to Repro
./testrunner -i /tmp/testexec.2350.ini -p get-cbcollect-info=True,GROUP=n1ql_op_without_timers -t eventing.eventing_rebalance.EventingRebalance.test_erl_crash_on_kv_and_eventing_node_during_eventing_rebalance,doc-per-day=20,dataset=default,nodes_init=5,services_init=kv-kv-eventing-eventing-index:n1ql,groups=simple,reset_services=True,handler_code=n1ql_op_without_timers,replicas=1,GROUP=n1ql_op_without_timers
|
I am aware there is a bug MB-30897 in the system test. However since the following error message is a generic error for all rebalance hang, I am tracking it as a new bug. Also this failure is only seen in this scenario where retry of the failed rebalance(because of killing erlang) fails.
[2018-08-13 11:24:00,280] - [rest_client:1598] ERROR - {u'status': u'none', u'errorMessage': u'Rebalance failed. See logs for detailed reason. You can try again.'} - rebalance failed
|
[2018-08-13 11:24:00,308] - [rest_client:3134] INFO - Latest logs from UI on 172.23.104.109:
|
[2018-08-13 11:24:00,308] - [rest_client:3135] ERROR - {u'node': u'ns_1@172.23.104.109', u'code': 0, u'text': u'Rebalance exited with reason {service_rebalance_failed,eventing,\n {rebalance_failed,\n {service_error,\n <<"eventing rebalance hasn\'t made progress for past 600 secs">>}}}', u'shortText': u'message', u'serverTime': u'2018-08-13T11:23:51.051Z', u'module': u'ns_orchestrator', u'tstamp': 1534184631051, u'type': u'critical'}
|
Logs attached.
I don't this is specific to n1ql operations from eventing, However if you think it is feel free to decrease the priority.
