[MDEV-17867] Make RESET MASTER throw GTID-related warning if gtid_slave_pos is set Created: 2018-11-28 Updated: 2020-06-11 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Admin statements, Replication |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Andrei Elkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
RESET MASTER resets gtid_binlog_pos, but not gtid_slave_pos. This means that gtid_current_pos can still contain GTIDs after RESET MASTER. This can result in some confusing behavior. See To try to make this more clear, what if RESET MASTER threw a warning if gtid_slave_pos was set? Maybe something like:
|
| Comments |
| Comment by Andrei Elkin [ 2020-06-11 ] |
|
GeoffMontee: To discuss with you, gtid_slave_pos represents the slave state, which may also be binlog-less. |
| Comment by Geoff Montee (Inactive) [ 2020-06-11 ] |
|
Hi Elkin,
Why would you want to deprecate the gtid_current_pos system variable? In my opinion, it is useful. It tells you the complete GTID position of the node when both the local GTID position and the slave GTID position are combined. This is a very useful system variable. I understand why you would want to deprecate CHANGE MASTER TO ... MASTER_USE_GTID=current_pos. I have no issue with that. However, I think the gtid_current_pos system variable is useful, even if CHANGE MASTER TO ... MASTER_USE_GTID=current_pos is unsupported. |
| Comment by Andrei Elkin [ 2020-06-11 ] |
|
GeoffMontee Sorry, I indeed meant MASTER_USE_GTID=current_pos. You may know better about user satisfaction of |