maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #05971
Help needed. Replication slave hangs on 'stop slave; '
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Thomas <thomas@plant.systems>
-
Date:
Mon, 1 Feb 2021 09:36:26 +0100
-
Arc-authentication-results:
i=1; ORIGINATING; auth=pass smtp.auth=thomas@plant.systems smtp.mailfrom=thomas@plant.systems
-
Arc-message-signature:
i=1; a=rsa-sha256; c=relaxed/relaxed; d=plant.systems; s=2018-10; t=1612168586; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=k7+/1CUB9s7ZZyCAEtClF6ovjZux/lwzWURMlGemvWU=; b=c9ABZA5+zAh+p/ln4aKeHIQ08iaSj5+F8Tx/rn0Wx23r+LUGcA25t8sJ1R/oFjuDMNlUif QtaOvnWrJA4rn2VUozgwF+nh/h5kjiAW1ZrinD4wsNz3uySSOyzkxSQFemOFMds8lMQyuf C9hhY0rbNqbM8mkQSnrohxCji+Lucjk9rmtSg25WoxHC7wIuNt1ZzvDb3qQ1DAWSt+CPHq LJKrAnCwapiUNBFSKg/wjVGe6cdwHAngB92MFQJLGwRYxvLqRaS3qcYb4YmeZTvRkmAMID YJgcqR0juWToke02QdMduupQbgVFC1YX91HRAffjFGvm7JNPi0CwquSM960YQA==
-
Arc-seal:
i=1; s=2018-10; d=plant.systems; t=1612168586; a=rsa-sha256; cv=none; b=eoeBeYE+bsRs1grKkMnR8slk/ggVUWK0vbNu37bfOPJsS1Aj2HZgzLvMBkMspvuWseIdtq u4ryKQDvqu2fntStu7BsiXVSmJMfDj9X+k9l+cMeuTp8jKz89Q8sunY1zvmxwBWfEFU2zc ElwdFj0zS+hfG0k1jwDWPWoze4i4Ge4nXQmhpcouCCJJtR2IILlXHsVBmleQwymuRcjLm2 IMnbj0cPXv2WbddHoiA4LKThQVr5ryDrm/MnT0H46FEPjDiMfoTSNRchtwjAg+S6SdoMFd ONISmhyi/cvAvx2jAi8mzlkM2SKW+RnVAq6dBVp1SqR+8IGhGHCMepc4wbBsbw==
-
Authentication-results:
ORIGINATING; auth=pass smtp.auth=thomas@plant.systems smtp.mailfrom=thomas@plant.systems
-
User-agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
Hello,
we have upgraded our MySQL Master/Slave server vom 10.1.24 to 10.1.48 on
25.01. Backups worked as usual, but since friday (29.01.) our backups do
not work anymore. I have seen that entering a 'stop slave;' on mysql cli
hangs forever, while in the background (on a second console, I see the
replication going on, but the gtid is far away from the master.
According to MaxScale, on the slave it is '0-1-8696229561 and on the
master '0-1-8705275411' and not moving forward on the slave.
Slave 'show slave status':
MariaDB [(none)]> show slave status\G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 172.16.1.1
Master_User: replication_user
Master_Port: 3306
Connect_Retry: 10
Master_Log_File: mysql-bin.005595
Read_Master_Log_Pos: 581894706
Relay_Log_File: relay-bin.000002
Relay_Log_Pos: 693
Relay_Master_Log_File: mysql-bin.005587
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 967647646
Relay_Log_Space: 8205026277
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_SSL_Crl:
Master_SSL_Crlpath:
Using_Gtid: Slave_Pos
Gtid_IO_Pos: 0-1-8705427292
Replicate_Do_Domain_Ids:
Replicate_Ignore_Domain_Ids:
Parallel_Mode: optimistic
1 row in set (0.00 sec)
Master status is this:
MariaDB [(none)]> show master status\G
*************************** 1. row ***************************
File: mysql-bin.005595
Position: 581594839
Binlog_Do_DB:
Binlog_Ignore_DB:
1 row in set (0.01 sec)
If I try to stop the server it hangs also. Waited half an hour after I
saw the backups hanging on the 'stop slave' command, then killed the
server with kill -9. It restarted without complaining, but the hang is
still occuring when doing a 'stop slave'.
Can anybody help me diagnosing and possibly resolving this issue?
Server is a baremetal with battery backed raid10. OS is Centos 7 all
updated.
Thanks,
Thomas
Follow ups