Hi,
Could you please clarify: by "not flushed" do you mean that the logs are not closed/re-opened? Or that they do not get rotated? Or that they do not get purged?
So far, given that the eventual problem is "disk full", I assume the latter, that old relay logs do not get purged automatically. However, I cannot reproduce it, seems to be working fine for me:
# Relay log files, after restart
|
slave-relay-bin.999998
|
slave-relay-bin.999999
|
slave-relay-bin.index
|
#
|
# Contents of relay-log.info:
|
./slave-relay-bin.999999
|
536
|
master-bin.000001
|
313
|
#
|
# Contents of relay index file:
|
./slave-relay-bin.999998
|
./slave-relay-bin.999999
|
#-----------------------------------------
|
flush relay logs;
|
#-----------------------------------------
|
# Relay log files
|
slave-relay-bin.1000000
|
slave-relay-bin.999999
|
slave-relay-bin.index
|
#
|
# Contents of relay-log.info:
|
./slave-relay-bin.1000000
|
492
|
master-bin.000001
|
313
|
#
|
# Contents of relay index file:
|
./slave-relay-bin.999999
|
./slave-relay-bin.1000000
|
#-----------------------------------------
|
flush relay logs;
|
#-----------------------------------------
|
# Relay log files
|
slave-relay-bin.1000000
|
slave-relay-bin.1000001
|
slave-relay-bin.index
|
#
|
# Contents of relay-log.info:
|
./slave-relay-bin.1000001
|
492
|
master-bin.000001
|
313
|
#
|
# Contents of relay index file:
|
./slave-relay-bin.1000000
|
./slave-relay-bin.1000001
|
#-----------------------------------------
|
flush relay logs;
|
#-----------------------------------------
|
# Relay log files
|
slave-relay-bin.1000001
|
slave-relay-bin.1000002
|
slave-relay-bin.index
|
#
|
# Contents of relay-log.info:
|
./slave-relay-bin.1000002
|
492
|
master-bin.000001
|
313
|
#
|
# Contents of relay index file:
|
./slave-relay-bin.1000001
|
./slave-relay-bin.1000002
|
|
select @@slave_parallel_threads, @@version;
|
@@slave_parallel_threads @@version
|
10 10.0.14-MariaDB-log
|
Files won't get purged if replication is stopped or aborted, but since you are saying that everything else works fine, I assume it is not the case.
Can you somehow demonstrate the problem? E.g. list the contents of the datadir, then run flush logs on the slave or or on the master, wait a bit, list the contents of the datadir again, the contents of relay-log.info file, and show slave status output?
Also, if you are using multi-source replication or some other non-standard replication setup, please do say so. And please attach your cnf file(s).
Thanks.
Hi,
Could you please clarify: by "not flushed" do you mean that the logs are not closed/re-opened? Or that they do not get rotated? Or that they do not get purged?
So far, given that the eventual problem is "disk full", I assume the latter, that old relay logs do not get purged automatically. However, I cannot reproduce it, seems to be working fine for me:
# Relay log files, after restart
slave-relay-bin.999998
slave-relay-bin.999999
slave-relay-bin.index
#
# Contents of relay-log.info:
./slave-relay-bin.999999
536
master-bin.000001
313
#
# Contents of relay index file:
./slave-relay-bin.999998
./slave-relay-bin.999999
#-----------------------------------------
flush relay logs;
#-----------------------------------------
# Relay log files
slave-relay-bin.1000000
slave-relay-bin.999999
slave-relay-bin.index
#
# Contents of relay-log.info:
./slave-relay-bin.1000000
492
master-bin.000001
313
#
# Contents of relay index file:
./slave-relay-bin.999999
./slave-relay-bin.1000000
#-----------------------------------------
flush relay logs;
#-----------------------------------------
# Relay log files
slave-relay-bin.1000000
slave-relay-bin.1000001
slave-relay-bin.index
#
# Contents of relay-log.info:
./slave-relay-bin.1000001
492
master-bin.000001
313
#
# Contents of relay index file:
./slave-relay-bin.1000000
./slave-relay-bin.1000001
#-----------------------------------------
flush relay logs;
#-----------------------------------------
# Relay log files
slave-relay-bin.1000001
slave-relay-bin.1000002
slave-relay-bin.index
#
# Contents of relay-log.info:
./slave-relay-bin.1000002
492
master-bin.000001
313
#
# Contents of relay index file:
./slave-relay-bin.1000001
./slave-relay-bin.1000002
select @@slave_parallel_threads, @@version;
@@slave_parallel_threads @@version
10 10.0.14-MariaDB-log
Files won't get purged if replication is stopped or aborted, but since you are saying that everything else works fine, I assume it is not the case.
Can you somehow demonstrate the problem? E.g. list the contents of the datadir, then run flush logs on the slave or or on the master, wait a bit, list the contents of the datadir again, the contents of relay-log.info file, and show slave status output?
Also, if you are using multi-source replication or some other non-standard replication setup, please do say so. And please attach your cnf file(s).
Thanks.