[MXS-803] Elected Master Sync across MaxScale instances Created: 2016-07-12 Updated: 2017-03-20 Resolved: 2017-03-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | galeramon |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Yorick Terweijden | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently when running two instance of MaxScale using priority for electing a Master it can happen that they have elected two different Masters. Having MaxScale sync it's elected Master across instances would be a great improvement. |
| Comments |
| Comment by markus makela [ 2017-03-20 ] |
|
This has been fixed in 2.1 where the galeramon only assigns master status to the node with the index of 1. |