Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.2.15
-
None
-
MXS-SPRINT-70
Description
It seems Maxscale doesn't detect master and do failover if master is down before maxscale restart.
[nil@centos68 rsandbox_mariadb-10_2_14]$ maxadmin list servers
|
Servers.
|
-------------------+-----------------+-------+-------------+--------------------
|
Server | Address | Port | Connections | Status
|
-------------------+-----------------+-------+-------------+--------------------
|
master | 127.0.0.1 | 24044 | 0 | Master, Running
|
slave1 | 127.0.0.1 | 24045 | 0 | Running
|
slave2 | 127.0.0.1 | 24046 | 0 | Running
|
-------------------+-----------------+-------+-------------+--------------------
|
[nil@centos68 rsandbox_mariadb-10_2_14]$
|
[nil@centos68 rsandbox_mariadb-10_2_14]$ sudo /etc/init.d/maxscale stop
|
Stopping MaxScale: [ OK ]
|
[nil@centos68 rsandbox_mariadb-10_2_14]$ master/stop
|
[nil@centos68 rsandbox_mariadb-10_2_14]$
|
[nil@centos68 rsandbox_mariadb-10_2_14]$ sudo /etc/init.d/maxscale start
|
Starting MaxScale: maxscale (pid 26334) is running... [ OK ]
|
[nil@centos68 rsandbox_mariadb-10_2_14]$
|
[nil@centos68 rsandbox_mariadb-10_2_14]$ maxadmin list servers
|
Servers.
|
-------------------+-----------------+-------+-------------+--------------------
|
Server | Address | Port | Connections | Status
|
-------------------+-----------------+-------+-------------+--------------------
|
master | 127.0.0.1 | 24044 | 0 | Down
|
slave1 | 127.0.0.1 | 24045 | 0 | Running
|
slave2 | 127.0.0.1 | 24046 | 0 | Running
|
-------------------+-----------------+-------+-------------+--------------------
|
[nil@centos68 rsandbox_mariadb-10_2_14]$
|
So if master is down and we start maxscale, it should do the failover, select any of the slave and make it to master.
Attachments
Issue Links
- is blocked by
-
MXS-2169 Split rejoin to two operations, add "enforce_simple_topology"-option
-
- Closed
-