Details
Description
In one of customers:
* rebalance was running
* node orchestrating rebalance failed
* node orchestrating rebalance was automatically failed over by new master
* node orchestrating rebalance re-joined (still thinking it was rebalancing seeMB-5049)
* we had config conflict and bad things as a result
Looks like during rebalance we should just disable autofailover because during rebalance humans can take care of correct actions
* rebalance was running
* node orchestrating rebalance failed
* node orchestrating rebalance was automatically failed over by new master
* node orchestrating rebalance re-joined (still thinking it was rebalancing see
* we had config conflict and bad things as a result
Looks like during rebalance we should just disable autofailover because during rebalance humans can take care of correct actions
Activity
Aliaksey Artamonau
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | autofailover should be auto failover anybody when rebalance is marked as in-progress. Or at least be more careful there | autofailover should not auto failover anybody when rebalance is marked as in-progress. Or at least be more careful there |
Aliaksey Artamonau
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Farshid Ghods
made changes -
| Labels | 1.8.1-release-notes |