[MXS-1923] The Desynced state of Galera Node is not given in maxctrl server list Created: 2018-06-13  Updated: 2024-01-04  Resolved: 2020-11-09

Status: Closed
Project: MariaDB MaxScale
Component/s: galeramon
Affects Version/s: None
Fix Version/s: 6.0.0

Type: New Feature Priority: Major
Reporter: Zdravelina Sokolovska (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: Galera

Epic Link: Monitor Improvements
Sprint: MXS-SPRINT-99, MXS-SPRINT-100, MXS-SPRINT-118

 Description   

The Desynced state of Galera Node is not given in maxctrl server list

When Galera Node was desynced from the group with setting up wsrep_desync,
the maxctrl is displaying just Running.
It would be more clear if give in addition the Desynced state in the maxctrl server list.

on server2 set wsrep_desync and FTWRL
check that Node gets in Desynced state
check the State of server2 from MaxScale Node via maxctrl list servers

MariaDB [(none)]> set global wsrep_desync=1 ;
Query OK, 0 rows affected (0.001 sec)
 
MariaDB [(none)]> flush tables with read lock ;
Query OK, 0 rows affected (0.000 sec)

check locally on server2 the wsrep state

 
MariaDB [(none)]> show status like "%state%" ;
+-------------------------------------------+--------------------------------------+
| Variable_name                             | Value                                |
+-------------------------------------------+--------------------------------------+
| Max_statement_time_exceeded               | 0                                    |
| Performance_schema_statement_classes_lost | 0                                    |
| wsrep_cluster_state_uuid                  | 3c15149f-5766-11e8-9a99-22bc53d40581 |
| wsrep_evs_state                           | OPERATIONAL                          |
| wsrep_local_state                         | 2                                    |
| wsrep_local_state_comment                 | Donor/Desynced                       |
| wsrep_local_state_uuid                    | 3c15149f-5766-11e8-9a99-22bc53d40581 |
+-------------------------------------------+--------------------------------------+
7 rows in set (0.001 sec)

The wsrep Desynced state of server is not displayed from the MaxScale Node

[root@t4w1 /]#  maxctrl list  servers
┌─────────┬─────────────────┬──────┬─────────────┬─────────────────────────┬──────┐
│ Server  │ Address         │ Port │ Connections │ State                   │ GTID │
├─────────┼─────────────────┼──────┼─────────────┼─────────────────────────┼──────┤
│ server1 │ 192.168.104.193 │ 3306 │ 0           │ Master, Synced, Running │      │
├─────────┼─────────────────┼──────┼─────────────┼─────────────────────────┼──────┤
│ server2 │ 192.168.104.195 │ 3306 │ 0           │ Running                 │      │
├─────────┼─────────────────┼──────┼─────────────┼─────────────────────────┼──────┤
│ server3 │ 192.168.104.196 │ 3306 │ 0           │ Slave, Synced, Running  │      │
└─────────┴─────────────────┴──────┴─────────────┴─────────────────────────┴──────┘



 Comments   
Comment by markus makela [ 2018-06-13 ]

Since MaxScale has no such server state nor does MaxAdmin show it, this should probably be filed as a new feature request rather than a bug.

Comment by markus makela [ 2018-06-13 ]

I changed this to a new feature request as it's a new state for the servers as well as a new concept inside MaxScale.

Comment by Johan Wikman [ 2020-03-02 ]

Changed to 2.6 as we will not do this for 2.5.

Generated at Thu Feb 08 04:10:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.