Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.incubator.apache.org
Received-SPF: error (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Ensemble Provider best practices
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: 
 <CADHGh9Xpya5nCtfqpjJZ1GTcpY_gOAjjQ9FiCX8KrWW19xO6Rg@mail.gmail.com>
Date: Mon, 29 Apr 2013 08:36:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <176C42DD-FE52-4C4D-9426-A3A57CCF37B9@jordanzimmerman.com>
References: 
 <CADHGh9Xpya5nCtfqpjJZ1GTcpY_gOAjjQ9FiCX8KrWW19xO6Rg@mail.gmail.com>
To: user@curator.incubator.apache.org

There is a bug either in Curator or ZooKeeper (I believe it's ZK) that =
causes the connection to hang and never reset. I'm working on a solution =
(it will be in the Apache version of Curator). So, yes, use =
EnsembleProvider.

On Apr 26, 2013, at 12:24 PM, Ioannis Canellos <iocanel@gmail.com> =
wrote:

> Hi,
>=20
> I have a case where the ensemble can change (by adding/removing zk =
servers) and I wanted to find the best approach on reconfiguring the =
curator framework.
> It seemed like a good idea to implement my custom ensemble provider, =
which would receive updates with the modified connectionString.=20
>=20
> This works fine, if I mark the zookeeper client as lost (so that the =
framework can pick the updated connection string from the =
EnsembleProvider).
> The problem is that after that the ConnectionStateListeners are not =
receiving any events for CONNECTED/RECONNECTED etc.
>=20
> Is this expected?
>=20
> Is there any other approach for changing the connection string, =
without recreating the CuratorFramework?=20
>=20
> Thanks in advance.
>=20