Re: [Maria-discuss] The relay-log is not fluashed after the slave-relay-log.999999 showed
Hi, Kristian. Frist of all, thanks for your quick reply. I think what you mentioned is the right way to go. In other words, the slave-relay-log.** files should be flushed as same as when using Slave_parallel_threads:0 setting. If there is any progress, please let me know. Thank you again. Best regards, - Jasung 2015-01-05 오후 6:38에 Kristian Nielsen 이(가) 쓴 글: Gmail next1...@gmail.com writes: And, as I mentioned at the title of this question, the relay-log is not flushed after the slave-relay-log.99 showed when using Salve_parallel_threads:10 setting. like showed blow. - binlog_format: ROW - Slave_parallel_threads:10 Everything are working fine except the slave-relay-log.** files continue to exist at the disk which will finally cause the disk full. If I change the value of Slave_parallel_threads setting from 10 to 0, the log will be flushed. Howevery PK duplicate warning error logs come next. Ok, thanks for reporting this. It's probably a bug that parallel replication behaves differently from non-parallel. I'll try to look into it when I have time. I could imagine that there are more bugs lurking when the log counter overflows... I'm not sure this is well tested. I wonder what the correct behaviour is? Should it just continue with slave-relay-log.100 ? Thanks, - Kristian. ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] The relay-log is not fluashed after the slave-relay-log.999999 showed
Gmail next1...@gmail.com writes: And, as I mentioned at the title of this question, the relay-log is not flushed after the slave-relay-log.99 showed when using Salve_parallel_threads:10 setting. like showed blow. - binlog_format: ROW - Slave_parallel_threads:10 Everything are working fine except the slave-relay-log.** files continue to exist at the disk which will finally cause the disk full. If I change the value of Slave_parallel_threads setting from 10 to 0, the log will be flushed. Howevery PK duplicate warning error logs come next. Ok, thanks for reporting this. It's probably a bug that parallel replication behaves differently from non-parallel. I'll try to look into it when I have time. I could imagine that there are more bugs lurking when the log counter overflows... I'm not sure this is well tested. I wonder what the correct behaviour is? Should it just continue with slave-relay-log.100 ? Thanks, - Kristian. ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
[Maria-discuss] The relay-log is not fluashed after the slave-relay-log.999999 showed
Hello, dear users. I am using MariaDB 10.0.14 at CentOS 6.5. And, as I mentioned at the title of this question, the relay-log is not flushed after the slave-relay-log.99 showed when using Salve_parallel_threads:10 setting. like showed blow. - binlog_format: ROW - Slave_parallel_threads:10 Everything are working fine except the slave-relay-log.** files continue to exist at the disk which will finally cause the disk full. If I change the value of Slave_parallel_threads setting from 10 to 0, the log will be flushed. Howevery PK duplicate warning error logs come next. Is there any setting should be used with Slave_parallel_threads setting? Any help will be great. Best regareds, - Jasung ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
