Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
MIME-Version: 1.0
In-Reply-To: <CAB5oV2_8ULm2+xPYPY7+QMDzwzg5SpL-Z37up3eJ3NS716BSTg@mail.gmail.com>
References: <1c79892c.4730.15471195e30.Coremail.wangyongqiang0617@163.com>
 <CAB5oV28Q+YSqKs7ecE4AvWNi3Nc75AgQC6bh6P57_CVnDxsR4A@mail.gmail.com>
 <CAB5oV29mJE54t2R1s=j51CwG8Gq2HyQxdJJaBOgWsNE1vatfLg@mail.gmail.com> <CAB5oV2_8ULm2+xPYPY7+QMDzwzg5SpL-Z37up3eJ3NS716BSTg@mail.gmail.com>
From: Alexander Shraer <shralex@gmail.com>
Date: Mon, 2 May 2016 15:00:58 -0700
Message-ID: <CANcXBFON4+E7-vG4PU_rJuQZi38GA8-jB2z91K6JHykLNS+xMQ@mail.gmail.com>
Subject: Re: how to make a server be leader permanently
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c123712d285e40531e321f8
archived-at: Mon, 02 May 2016 22:01:22 -0000

--94eb2c123712d285e40531e321f8
Content-Type: text/plain; charset=UTF-8

If you're interested to work on something like that, a good starting point
could be
implementing a leader handoff API: ZOOKEEPER-2076

On Mon, May 2, 2016 at 4:19 AM, Flavio P JUNQUEIRA <fpj@apache.org> wrote:

> We don't have this kind of behavior enabled because it'd affect
> availability. If your single leader fails, then the zookeeper ensemble
> becomes unavailable until the server comes back and might require manual
> intervention if the server is permanently down.
>
> Also, upon recovery, the configured leader might not have the most recent
> committed state,  which could cause you to lose data.
>
> The bottom line is that you can't really force this kind of behavior
> currently with zookeeper.
>
> -Flavio
> On 2 May 2016 11:53, "WangYQ" <wangyongqiang0617@163.com> wrote:
>
> i want to make a server with lower load be the zookeeper leader
> permanently. is there any method or configuration?
>

--94eb2c123712d285e40531e321f8--