<br><br><div class="gmail_quote">On Mon, Jul 2, 2012 at 1:33 PM, Alan Runyan <span dir="ltr"><<a href="mailto:runyaga@gmail.com" target="_blank">runyaga@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> So an error is raised and logged, but with the cache being cleared so that<br>>> on the second try it reconnects? My rational for this change is that If<br>>> your doing a hot failover that means that a) something bad has happened to<br>
>> main server and the recovery of those transactions probably won't happen any<br>>> way or b) it happened during a maintenance window/the failover is happening<br>>> for convenience and any difference between the two servers are probably<br>
>> minor, such as session data. With b. the server admin would be in the<br>>> position to restore the main server anyways.<br>
<br>
</div>>Sounds reasonable. Does the "drop rather than verify" feature get verified when<br>>connecting to a new replica? Should it?<br></blockquote><div>I was thinking that it would be True of False from configuration with the current behavior(drop == False) being the default. So in practice, verification happens on startup of the zeo client.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">>--<br>>Alan Runyan<br>
<br><br>
</font></span></blockquote></div><br>