Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Incomplete
-
10.4.25
-
CENTOS 7.9
Description
Hello,
After migration from 10.4.18 to 10.4.25 the replication lag.
When I look at metadata_lock_info I see 2 "MDL_BACKUP_COMMIT" and 2 "MDL_BACKUP_TRANS_DML".
Those locks seems to be from the slave processes ...
If I kill the threads the slaves ptocesses are stopped.
If i restart the slaves, they are working some time (high IO rate) and the lMDL_BACKUP locks comes back and the replication lag again.
It is very urgent as it is on a production system.
The migration to 10.4.25 was OK on integration and pre-production systems and even on some other smaller production systems.
That system is working at 30000/50000 updates per minute.
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
Hi jppo
Since it will not be possible to be reproduced from your end, if you could provide general production binary logs that you think would cause the problem in 10.4.25, we could try to see what would be the difference between 10.4.18 and 10.4.25. Please use the FTP server.
Also, is only one master receiving queries, or are both masters receiving queries?
Hello,
I come back after a long time ... with no news. The binary logs are destroyed after 4/5 days ..... as they are huge.(65 to 100 files a day).
Only one machine receive updates, the scond one is used as read only by some applications, but it is 1% of the activity.
The client accesses machine through Virtual IPs managed by a High Availability system with a higher priority on the "001" system, the other "002" uses a smaller priority to avoid conflicts.
I think that we do stop the 10.4 migration and begin tests to go to a newer version which is "compatible" at replication level as our systems are running 24/24 and 365/365. We uses to use that kind of migration since the "Mysql" time.
which version will be perfectly compatible at the replication level with the 10.4.18 ?
Hello,
Is the replication process compatible between major versions ?
From 10.4.18 toward what version could we migrate with no replication problems ?
Thanks for advance
JP P
Yes, replication should be compatible between major versions. Please consult:
https://mariadb.com/kb/en/upgrading-between-major-mariadb-versions/
https://mariadb.com/kb/en/replication-overview/#cross-version-replication-compatibility
If you run into an issue which you believe is a bug, please report it by following these guidelines: https://mariadb.com/kb/en/reporting-bugs/
Hi jppo
The output from show processlist would provide more information, as well as the binary and error logs and show slave status output to see if there is a bug and if it can be reproduced.