[MXS-4165] Servers with priority=0 are selected as Master Created: 2022-06-14 Updated: 2023-07-04 Resolved: 2022-06-17 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | galeramon |
| Affects Version/s: | 2.5.20, 6.4.0 |
| Fix Version/s: | 2.5.21, 6.4.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
The galeramon documentation for the priority parameters mentions that nodes with a non-negative priority value are never selected as the Master node of the cluster. The code appears to be wrong and instead of ignoring servers with priority=0, it ends up ignoring the node priority if all other nodes are gone. The reason why it ends up accepting them is because the default value of priority is 0. |
| Comments |
| Comment by markus makela [ 2022-06-14 ] |
|
I think the least breaking change we can do is to make priority accept negative values and then amend the galeramon documentation. This means that nodes with zero values are selected if no nodes with positive values are found and negative priority values cause a node to never be selected as Master. |