Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.0.5, 2.1.2
-
None
-
2017-39
Description
On practice it may be very unpleasant situation when maxscale service is restarted and server 'maintenance' bits are not preserved.
The restart may happen accidentally or because of some software/hardware problem or result of software bug or result of threat, etc
Thus server 'maintenance' flag must survive service restart.
MaxScale> list servers
|
Servers.
|
-------------------+-----------------+-------+-------------+--------------------
|
Server | Address | Port | Connections | Status
|
-------------------+-----------------+-------+-------------+--------------------
|
server1 | 127.0.0.1 | 3307 | 0 | Maintenance, Master, Running
|
-------------------+-----------------+-------+-------------+--------------------
|
MaxScale> exit
|
$ killall maxscale
|
Shutting down MaxScale
|
$ bin/maxscale --basedir=$(pwd)
|
$ bin/maxadmin
|
MaxScale> list servers
|
Servers.
|
-------------------+-----------------+-------+-------------+--------------------
|
Server | Address | Port | Connections | Status
|
-------------------+-----------------+-------+-------------+--------------------
|
server1 | 127.0.0.1 | 3307 | 0 | Master, Running
|
-------------------+-----------------+-------+-------------+--------------------
|