[MXS-1678] Stopping IO thread on relay master causes it to be promoted as master Created: 2018-02-21 Updated: 2018-03-12 Resolved: 2018-03-01 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbmon |
| Affects Version/s: | 2.1.13 |
| Fix Version/s: | 2.1.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
With a four server setup consisting of two master-slave pairs, A→B and C→D where A and C are masters, configuring C to replicate from A will form a multi-tiered replication topology (i.e. C will be a relay master).
When the IO thread on C (server3) is stopped, it will be "promoted" as a master server.
If C disconnects from A, it should not be treated as a master server. |
| Comments |
| Comment by markus makela [ 2018-03-01 ] |
|
The master_id was not stored if the IO thread was stopped. |