Version:mysql-5.1-telco-6.3OS:Linux (debian etch) Assigned to:MySQL Verification TeamCPU Architecture:Any Tags:5.1.27-ndb-6.3.17-telco,cluster,MySQL,replication [16 May 2008 13:57] Cyril SCETBON Description:SQL_THREAD stop cause of the following error : It was not possible to update the po...
Description: repeated stop sql_thread/start sql_thread on a slave with GTID enabled may cause it to log a transaction ignoring the corresponding gtid for that transaction received from master. Transaction from master SET @@SESSION.GTID_NEXT='master_uid:100' BEGIN; INSERT INTO t1 values(1); ...
"start slave not allowed when raft has stopped SQL threads"); return true; } (void)invoked_by_raft; if (load_mi_and_rli_from_repositories(mi, false, thread_mask)) { is_error = true; my_error(ER_MASTER_INFO, MYF(0)); @@ -9651,6 +9678,11 @@ int raft_stop_sql_thread(THD ...
Bug #91671stop slave sql_thread for channel 'group_replication_applier' could not return Submitted:17 Jul 2018 2:08Modified:27 Nov 2018 12:05 Reporter:Zhenghu Wen(OCA)Email Updates: Status:ClosedImpact on me: None Category:MySQL Server: Group ReplicationSeverity:S3 (Non-critical) ...
repl --force --exec-after=/root/wbw/fo_after.sh --daemon=start After a while stop it using: mysqlfailover --master=fo --discover-slaves-login=fo --log=/tmp/fo.log --rpl-user=repl:repl --force --exec-after=/root/wbw/fo_after.sh --daemon=stop the sql_thread of the slave ...