hadoop-zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Session expiration caused by time change
Date Thu, 19 Aug 2010 15:39:16 GMT
True.  But it knows that there has been a jump.

Quiet time can be distinguished from clock shift by assuming that members of
the cluster
don't all jump at the same time.

I would imagine that a "recent clock jump" estimate could be kept and
buckets that would
otherwise expire due to such a jump could be given a bit of a second lease
on life, delaying
all of their expiration.  Since time-outs are relatively short, the server
would be able to forget
about the bump very shortly.

On Thu, Aug 19, 2010 at 8:22 AM, Benjamin Reed <breed@yahoo-inc.com> wrote:

> if we try to use network messages to detect and correct the situation, it
> seems like we would recreate the problem we are having with ntp, since that
> is exactly what it does.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message