[Maria-discuss] Semi-sync replication hangs when changing binlog filename.
Hi,
I am using semi-sync replication with the `rpl_semi_sync_master_timeout` set to a very high value to ensure commits aren't committed on the master unless they have been replicated to the slave.
However whenever the binlog filename changes the replication stalls indefinitely.
A trace of this interaction between the master and the semi-sync slave is here:
https://gist.github.com/josephglanville/e87ae96b9be9125427b58cd3a43d5c1e
The semi-sync settings I have configured on the master are:
rpl_semi_sync_master_wait_point = "AFTER_SYNC"
rpl_semi_sync_master_timeout = 18446744073709551615 # effectively infinite as we don't want to fallback to async repl
rpl_semi_sync_master_enabled = 1
rpl_semi_sync_master_wait_no_slave = 1 # don't allow writes if slave isn't connected
Up until the binlog filename change everything works as expected.
Anyone have any ideas on how to fix the problem or is this a bug in semi-sync replication?
Joseph.
Hi Joseph,
On Fri, Jul 29, 2016 at 10:11 AM, Joseph Glanville jpg@jpg.id.au wrote:
However whenever the binlog filename changes the replication stalls indefinitely.
Interesting! I may have reproduced this, but it was only a quick test. Let me (or someone else) dig into this more.
Thanks for reporting this. -will
By "binlog filename changes" you mean when master starts writing binlogs into a new file? Can you clarify how the replication stalls? What "show processlist" shows at that time on master and on slave? What does "show slave status" show on the slave?
On Thu, Jul 28, 2016 at 10:03 PM, Will Fong will.fong@mariadb.com wrote:
Hi Joseph,
On Fri, Jul 29, 2016 at 10:11 AM, Joseph Glanville jpg@jpg.id.au wrote:
However whenever the binlog filename changes the replication stalls indefinitely.
Interesting! I may have reproduced this, but it was only a quick test. Let me (or someone else) dig into this more.
Thanks for reporting this. -will
-- Will Fong, Senior Support Engineer MariaDB Corporation
_______________________________________________ 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
The process list shows that the query is blocked waiting for back from semi sync slave. I can post further information shortly, AFK currently.
Cheers, Joseph.
Get Outlook for Androidhttps://aka.ms/ghei36
On Fri, Jul 29, 2016 at 3:08 PM +1000, "Pavel Ivanov" <pivanof@google.commailto:pivanof@google.com> wrote:
By "binlog filename changes" you mean when master starts writing binlogs into a new file? Can you clarify how the replication stalls? What "show processlist" shows at that time on master and on slave? What does "show slave status" show on the slave?
On Thu, Jul 28, 2016 at 10:03 PM, Will Fong will.fong@mariadb.com wrote:
Hi Joseph,
On Fri, Jul 29, 2016 at 10:11 AM, Joseph Glanville jpg@jpg.id.au wrote:
However whenever the binlog filename changes the replication stalls indefinitely.
Interesting! I may have reproduced this, but it was only a quick test. Let me (or someone else) dig into this more.
Thanks for reporting this. -will
-- Will Fong, Senior Support Engineer MariaDB Corporation
_______________________________________________ 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
participants (3)
-
Joseph Glanville -
Pavel Ivanov -
Will Fong