Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Mon, 25 Mar 2013 09:26:42 +0000
From: Ivan Kelly <ivank@apache.org>
To: user@zookeeper.apache.org
Subject: Re: What should I do with SyncDisconnected
Message-ID: 
 <20130325092641.GC6908@ip-10-228-174-15.eu-west-1.compute.internal>
References: 
 <20130313210140.GD17815@ip-10-228-174-15.eu-west-1.compute.internal>
 <F4DAFAE5-9311-4D9F-8C73-9F6B5E746D71@jordanzimmerman.com>
 <CABaj-QaR14gR1trZOovY7sbAokR+E7Cga6_8jd-FRf+S+QaQ5A@mail.gmail.com>
 <20130314213002.GA22759@ip-10-228-174-15.eu-west-1.compute.internal>
 <3DA70000-603D-4D4A-B373-CDD52BA1ADF1@jordanzimmerman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DA70000-603D-4D4A-B373-CDD52BA1ADF1@jordanzimmerman.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Mar 14, 2013 at 02:43:58PM -0700, Jordan Zimmerman wrote:
> > But how long to wait? If the server is truly partitioned from ZK, then
> > I'll wait forever, and the client request will be hung forever.
> Curator waits for the time specified as the "connection
> timeout". Curator introduces three connection states, CONNECTED,
> SUSPENDED and LOST. When SysDisconnected is received, Curator sets
> the state to SUSPENDED and then issues a sync() in the
> background. This sync() does through Curator's normal connection
> management, retries, etc. If the sync() doesn't succeed within the
> connection timeout, Curator sets the state to LOST. How the
> application handles these state changes is, of course, up to the
> app.  
Sorry for the late reply.

The connection timeout is defined in curator though? Or is taken from
the session timeout? We're doing something like this now.

-Ivan