Description
Build: 6.6.0 build 7917
Test :
- Create 4 node cluster 2 KV , 1 eventing , 1 N1QL:index
- Create 10 buckets
- Deploy 2 handler
- Failover 1 kv node
- Add back failover node and full recovery
- When rebalance for the last bucket is completed around ~90%, deploy 1 more handler
- Rebalance will fail with
Rebalance exited with reason {service_rebalance_failed,eventing,
|
{worker_died,
|
{'EXIT',<0.30052.79>,
|
{{badmatch,
|
{error,
|
{bad_nodes,eventing,prepare_rebalance,
|
[{'ns_1@172.23.106.73',
|
{error,
|
{unknown_error,
|
<<"Some apps are deploying or resuming on some or all Eventing nodes">>}}}]}}},
|
[{service_rebalancer,rebalance_worker,1,
|
[{file,"src/service_rebalancer.erl"},
|
{line,164}]},
|
{proc_lib,init_p,3,
|
[{file,"proc_lib.erl"},{line,232}]}]}}}}.
|
Rebalance Operation Id = 50d80d59791945ddf21089e29de64db0
|
Observed: Rebalance is disabled even though rebalance is failed. Hence customer is not able to retry failed rebalance
Attachments
Issue Links
- backports to
-
MB-42800 Eventing: Rebalance button disabled for failed rebalance
-
- Closed
-
| For Gerrit Dashboard: MB-42830 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 140621,11 | MB-42830 : Report correct isBalanced state on rebalance failure | unstable | eventing | Status: ABANDONED | 0 | 0 |
| 140781,7 | MB-42830 : Report correct isBalanced state on rebalance failure | unstable | eventing | Status: MERGED | +2 | +1 |
| 140911,2 | MB-42830 : read isBalanced holding the mu lock | unstable | eventing | Status: MERGED | +2 | +1 |