Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Subject: ntp adjust to zookeeper
Date: Thu, 23 Jun 2011 10:48:01 +0800
Message-ID: <7DA4B654C7FEB24C9998EE4867BEE93EBC74D2@CNMAIL12.cn.utstarcom.com>
In-Reply-To: <BANLkTi=nmq8aVVqcoDN=mVw=PpTYdgxL9w@mail.gmail.com>
Thread-Topic: ntp adjust to zookeeper
Thread-Index: AcwxSwudUpzIx4a8Q6aRvKFFJ1eBswAAkNww
References: <7DA4B654C7FEB24C9998EE4867BEE93EBC74BE@CNMAIL12.cn.utstarcom.com>
 <BANLkTi=nmq8aVVqcoDN=mVw=PpTYdgxL9w@mail.gmail.com>
From: "Donna Li" <donna.li@utstar.com>
To: <user@zookeeper.apache.org>


my server configuration is as following:
tickTime=3D1000
initLimit=3D5
syncLimit=3D2

client api:
zookeeper_init(,,recv_timeout=3D2000,)

So client will session expire by 2s if server can not receive the =
heartbeat. Does the ntp max jump time =3D 2s?


-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: Ted Dunning [mailto:ted.dunning@gmail.com]=20
=B7=A2=CB=CD=CA=B1=BC=E4: 2011=C4=EA6=D4=C223=C8=D5 10:12
=CA=D5=BC=FE=C8=CB: user@zookeeper.apache.org
=D6=F7=CC=E2: Re: ntp adjust to zookeeper

Large time jumps can cause problems because your sessions may expire
surprisingly.

It is best to keep your servers within a tight tolerance.  Time jumps =
may
occur more seriously if you are using an over-subscribed VM (think small =
EC2
instances).  That can seriously confuse NTP and cause real problems.

On Wed, Jun 22, 2011 at 6:34 PM, Donna Li <donna.li@utstar.com> wrote:

> All:
>
>        Could zookeeper cluster servers work normal after ntp adjust?
>
>
>
>
>
> Best Regards
>
> Donna li
>
>