maxscale.dat
syslog.dat
[MXS-831] new_master event not triggered by galeramon Created: 2016-08-12 Updated: 2024-02-02 Resolved: 2016-09-30 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | galeramon |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Sylvain ARBAUDIE | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) maxadmin Version 1.4.3 Server version: 5.5.50-MariaDB-1~wheezy-wsrep mariadb.org binary distribution, srep_25.14.r9949137 |
||
| Attachments: |
maxscale.dat
syslog.dat
|
| Description |
|
when a master of a galeramon goes down, the new_master event doesn't seem to trigger during the lifecycle and only at the startup of maxscale. besides, master_dwon event is also not triggered each and everytime a master node goes down which is somewhat disturbing for the writing of automated failover scripts. |
| Comments |
| Comment by markus makela [ 2016-09-26 ] |
|
The change from master to slave and vice versa was detected as a loss type event. It is better to detect this event as a new_master event instead of a lost_slave event. |
| Comment by markus makela [ 2016-09-30 ] |
|
The new_master event is now properly detected if a slave is promoted to a master. |