[MDEV-8194] After START SLAVE UNTIL master_gtid_pos = ... the IO thread also stops, needs to be documented Created: 2015-05-20  Updated: 2015-06-10  Resolved: 2015-06-10

Status: Closed
Project: MariaDB Server
Component/s: Documentation, Replication
Affects Version/s: 10.0, 10.1
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: None


 Description   

In the traditional START SLAVE UNTIL, after the desired position is reached, the SQL thread stops, but the IO thread does not. With START SLAVE UNTIL MASTER_GTID_POS = ... both threads stop. It's apparently expected, but it needs to be documented in the KB (https://mariadb.com/kb/en/mariadb/global-transaction-id/#start-slave-until-master_gtid_posxxx), I couldn't find it there.

More generally, as I understand, this flavor of UNTIL actually applies to the IO thread, while the traditional one only affects the SQL thread. It reads between the lines in the abovementioned KB article, but it would be nice to emphasize it i it's true.



 Comments   
Comment by Kristian Nielsen [ 2015-06-10 ]

I've updated the knowledge base page. START SLAVE UNTIL master_gtid_pos=xxx actually affects both the IO and the SQL thread, as well as the binlog dump thread on the master server.

Generated at Thu Feb 08 07:25:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.