Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
any version
Description
Maxscale requires GTID repl for failover but servers show gtid by default. I would like a better display of information on this since if a slave is rebuilt and misconfigured with basic binlog_pos it at a glance looks like maxscale is heathy but is in fact no longer HA. This is disastrous if a master goes and stays down to get a replica promoted.
For usability a display like below is ideal to see what the current service status really is
[ACME] root@maxscale-1: etc # maxctrl list servers
|
┌───────────┬──────────────┬──────┬─────────────┬─────────────────┬────────┬─────────────────┐
|
│ Server │ Address │ Port │ Connections │ State │ GTID │ Monitor │
|
├───────────┼──────────────┼──────┼─────────────┼─────────────────┼────────┼─────────────────┤
|
│ fooshop-1 │ 131.21.1.185 │ 3306 │ 0 │ Master, Running │ 0-1-90 │ MariaDB-Monitor │
|
├───────────┼──────────────┼──────┼─────────────┼─────────────────┼────────┼─────────────────┤
|
│ fooshop-2 │ 131.21.1.248 │ 3306 │ 0 │ Slave, Running │ NOT USING GTID REPL │ MariaDB-Monitor │
|
├───────────┼──────────────┼──────┼─────────────┼─────────────────┼────────┼─────────────────┤
|
│ fooshop-3 │ 131.21.1.89 │ 3306 │ 0 │ Slave, Running │ NOT USING GTID REPL │ MariaDB-Monitor │
|
└───────────┴──────────────┴──────┴─────────────┴─────────────────┴────────┴─────────────────┘
|
The slaves here are clearly configured but ineligible for failover
Attachments
Issue Links
- relates to
-
-
- In Review
-