[MXS-3174] read gtid_current_position Created: 2020-09-11 Updated: 2020-09-11 Resolved: 2020-09-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxadmin |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | febriyant | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | GTID, api, maxscale | ||
| Environment: |
Centos 7 |
||
| Description |
|
currently i have 3 node with replication GTID
on api maxscale (v1/monitors) we got gtid_current_post at my question is whats the paramater is real as gtid_position because we see the different gtid_current_position from maxscale api ? and i check slave status on server-99 we got this is wrong i read or information from maxscale is wrong ? |
| Comments |
| Comment by markus makela [ 2020-09-11 ] | |||||||||||||||||||||
|
Gtid_IO_Pos is the latest replicated GTID position and gtid_current_pos is the highest GTID position on the current server (replicated from elsewhere or generated on the server itself). You can use this query to check the GTID position on a server:
| |||||||||||||||||||||
| Comment by febriyant [ 2020-09-11 ] | |||||||||||||||||||||
|
so when i get valid gtid from maxscale API is gtid_io_pos
| |||||||||||||||||||||
| Comment by markus makela [ 2020-09-11 ] | |||||||||||||||||||||
|
The values returned from the REST API are the values returned by the following queries:
They are updated once every monitor_interval. |