Hi,<div><br><div class="gmail_quote">2013/3/14 Michael Widenius <span dir="ltr">&lt;<a href="mailto:monty@askmonty.org" target="_blank">monty@askmonty.org</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>I didn&#39;t think that sync_binlog=1 is required anymore for safe reliction.<br>
<br>
We are always using group commit in MariaDB 10.0 for the master, so<br>
the binary log will be synced for each group commit, which is safe.<br></blockquote><div><br></div><div>I have to use it in a DRBD config. When testing this config, I killed mysqld with SIGKILL and sync_binlog=0 and failover start binary log in old position, that caused duplicates on slaves.</div>
<div><br></div><div>With sync_binlog=1, this happens no more.</div><div><br></div><div>How to configure how often group commits are fdatasynced ?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This is of course something that a customer can sponsor us, if they think<br>
this would be useful for them....<br></blockquote><div><br></div><div>We will discuss about that on March 27 ;)</div></div><div><br></div>-- <br>Greg
</div>