[MDEV-20240] Master/Master slave sync not working Created: 2019-08-02  Updated: 2019-08-16  Resolved: 2019-08-16

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1.41
Fix Version/s: 10.2.27, 10.1.42, 10.3.18, 10.4.8

Type: Bug Priority: Major
Reporter: Rune Torgersen Assignee: Andrei Elkin
Resolution: Fixed Votes: 3
Labels: None
Environment:

Ubuntu 16.04 using http://ftp.osuosl.org/pub/mariadb/repo/10.1/ubuntu xenial main as repository


Attachments: File localconf.cfg    
Issue Links:
Duplicate
duplicates MDEV-20247 Replication hangs with "preparing" an... Closed

 Description   

Hi.
Were running mariadb in master/master configuration o two servers. After upgrading to 10.1.41, the slave sync stopped working.
show slave status shows nothing wrong, but the server will hang when issuing "stop slave".
also no message sare syncronized.

Reverting server to 10.1.40 fixes problem.
Both upgrading an existing working install, and starting from scratch fails the same way.
The configuration we use have worked for us for about three years .

I do not know what type of info is needed to diagnose the issue.

Attached is the server config file from /etc/mysql/conf.d. Default my.cfg from installer package is used.

Initial sync is started by copying the main db from one unit to the other, and tehn setting the binlog position:
set global gtid_slave_pos='position fro other server'
and starting sync:
change master to master_host='controlserver2', master_user='replication', master_password='${pw}', master_use_gtid=slave_pos;";



 Comments   
Comment by bulepage [ 2019-08-05 ]

same issue in 10.3.17

Comment by MG [ 2019-08-05 ]

This seems to be a duplicate of MDEV-20247 which currently has a larger number of watchers and lists additional affected versions

Comment by Rune Torgersen [ 2019-08-06 ]

Yes MDEV-20247 looks to be the same issue.

Comment by Sujatha Sivakumar (Inactive) [ 2019-08-16 ]

Fix for this issue is implemented as part MDEV-20247.

Generated at Thu Feb 08 08:57:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.