[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, on server2 set wsrep_desync and FTWRL
check locally on server2 the wsrep state
The wsrep Desynced state of server is not displayed from the MaxScale Node
|
| 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. |