Details
-
Improvement
-
Resolution: Fixed
-
Critical
-
6.0.4, 6.5.1, 6.6.0, Cheshire-Cat
-
1
Description
Although this behaviour is as per design, this ticket is to investigate if things can be improved in fail-over scenario. There may be some complications in forcefully taking over VB ownership without a rebalance. Especially if recovery is performed soon after marking a node failed-over (without rebalance).
Attachments
Issue Links
For Gerrit Dashboard: MB-40636 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
134291,3 | MB-40636 : automatically redistribute vbs to active nodes on node failover | mad-hatter | eventing | Status: MERGED | +2 | +1 |
134292,3 | MB-40636 : Handle race in back-to-back failover of multiple eventing nodes | mad-hatter | eventing | Status: MERGED | +2 | +1 |
134341,2 | MB-40636 : Rename ERR_REBALANCE_ONGOING to ERR_REBALANCE_OR_FAILOVER_ONGOING | mad-hatter | eventing | Status: MERGED | +2 | +1 |
134604,2 | MB-40636 : turn on auto-redistribute-vbs-on-failover by default | mad-hatter | eventing | Status: MERGED | +2 | +1 |