[ZODB-Dev] zeo server hot failover

Kevin Kalupson kevin.kalupson at gmail.com
Mon Jul 2 19:22:13 UTC 2012


On Mon, Jul 2, 2012 at 1:33 PM, Alan Runyan <runyaga at gmail.com> wrote:

> > So an error is raised and logged, but with the cache being cleared so
> that
> >> on the second try it reconnects?  My rational for this change is that If
> >> your doing a hot failover that means that a) something bad has happened
> to
> >> main server and the recovery of those transactions probably won't
> happen any
> >> way or b) it happened during a maintenance window/the failover is
> happening
> >> for convenience and any difference between the two servers are probably
> >> minor, such as session data.  With b. the server admin would be in the
> >> position to restore the main server anyways.
>
> >Sounds reasonable.  Does the "drop rather than verify" feature get
> verified when
> >connecting to a new replica? Should it?
>
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.

>--
> >Alan Runyan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/zodb-dev/attachments/20120702/a21f9eac/attachment.html>


More information about the ZODB-Dev mailing list