[MDEV-9339] Can purge relay log when using multi-source Created: 2015-12-29  Updated: 2016-02-10  Resolved: 2016-02-10

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0.19
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: liuyang Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback, replication
Environment:

centos 6 x86.64


Attachments: Text File command_log.txt    
Issue Links:
Relates
relates to MDEV-9544 FLUSH [RELAY] LOGS does not rotate lo... Closed

 Description   

I can't purge replay logs when using multi-source replication

I have uploaded a work log



 Comments   
Comment by Elena Stepanova [ 2016-01-11 ]

There is certainly a problem, at least the fact that flush logs does not rotate relay logs for the named slave.

However, it does not explain why your old logs do not get purged. Logs 000001 and 000002 are old enough to be removed.
This part works for me, so there should be something more than just multi-source replication:

MariaDB [test]> system ls -l data2/*relay*
-rw-rw---- 1 user disk  62 Jan 11 01:47 data2/relay-log-m_1.info
-rw-rw---- 1 user disk 788 Jan 11 01:47 data2/wheezy-64-relay-bin-m_1.000002
-rw-rw---- 1 user disk 492 Jan 11 01:47 data2/wheezy-64-relay-bin-m_1.000003
-rw-rw---- 1 user disk  66 Jan 11 01:47 data2/wheezy-64-relay-bin-m_1.index
MariaDB [test]> 
MariaDB [test]> flush relay logs;
Query OK, 0 rows affected (0.46 sec)
 
MariaDB [test]> system ls -l data2/*relay*
-rw-rw---- 1 user disk  62 Jan 11 01:48 data2/relay-log-m_1.info
-rw-rw---- 1 user disk 549 Jan 11 01:48 data2/wheezy-64-relay-bin-m_1.000003
-rw-rw---- 1 user disk 492 Jan 11 01:48 data2/wheezy-64-relay-bin-m_1.000004
-rw-rw---- 1 user disk  66 Jan 11 01:48 data2/wheezy-64-relay-bin-m_1.index

Are you using parallel replication? Could you please attach your cnf file(s)?

Comment by Elena Stepanova [ 2016-02-10 ]

I've extracted the FLUSH LOGS problem into a separate JIRA entry: MDEV-9544. However, it does not explain why your old relay log files are not purged. If you have more information on the issue, please comment to re-open.

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