Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Garret Hayes <ghayes@cacheiq.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Date: Mon, 12 Mar 2012 21:02:21 -0400
Subject: Re: Cool news on the Curator/Exhibitor front - rolling
 release/upgrade
Thread-Topic: Cool news on the Curator/Exhibitor front - rolling
 release/upgrade
Thread-Index: Ac0AtQQPA8a4ntwHQNq+qTTJZ8vhcw==
Message-ID: <E16FAB8B-412C-4543-945F-066B335AC403@cacheiq.com>
References: <CB83D584.16083%jzimmerman@netflix.com>
In-Reply-To: <CB83D584.16083%jzimmerman@netflix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Woohoo! This is great news Jordan!=20

On 12.03.2012, at 18:32, "Jordan Zimmerman" <jzimmerman@netflix.com> wrote:

> I'm pretty excited about this one so I want to pre-annouce it. I'm curren=
tly working on rolling release/upgrade support in Exhibitor and Curator.
>=20
> For Exhibitor:
>    * Ensemble list, config values, etc. are centralized (via Amazon S3, a=
 shared file, etc.)
>    * If the ensemble list changes, Exhibitor will stage the change so tha=
t each instance in the ensemble
>       applies the change one at a time, thus accomplishing a rolling rele=
ase
>    * New servers can be added to the ensemble this way without taking dow=
n the cluster
>=20
> For Curator:
>    * Curator can now be configured to poll the Exhibitor instances to get=
 the list of ZK servers in the ensemble
>    * Curator will use the updated ensemble list when creating connections=
.
>    * If a Sys-Disconnected is received and there is a new ensemble list, =
Curator will close the current ZK
>       handle and create a new one using the updated list.
>=20
> Coming soon!
>=20
> -Jordan