Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99FBA17DB1 for ; Fri, 10 Oct 2014 13:27:07 +0000 (UTC) Received: (qmail 6294 invoked by uid 500); 10 Oct 2014 13:27:06 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 6256 invoked by uid 500); 10 Oct 2014 13:27:06 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 6236 invoked by uid 99); 10 Oct 2014 13:27:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 13:27:06 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shralex@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-vc0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 13:26:41 +0000 Received: by mail-vc0-f174.google.com with SMTP id hq12so2572485vcb.5 for ; Fri, 10 Oct 2014 06:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=L5Kr7ffEc1JZpti6qsuIt+wx1y21qjG+HWERSTzDcT0=; b=GO+oLxcSPJoYIShsLJZyuvseT+ZPm56cH1Pu1Olp3VYarGUhv8zKZ3XPeaoUy8NHlZ BgNhllFLYT+Ayo4Cw8U73sD2Du8d5XqjzUAKYeVhDpkPoQEpL5H9kKlgwJtWYUCDBbY3 GyJXPePZ5SisRBUgSXjXk9tg447mnOf2dtTDfO2NBBad/ZEAM9tAtwZ9tNbCpGXKMUmg bffaQPG2JSVBGphcWDybXF+LEjnacKNFZVbLW/rViVoYm5zFvK2KLjLAZkY9sTaKC810 /mFf2/vitkoW9aHeZauSlbYCmBwfNR6d+wYohiiK8v3k2QUTFInuEtUOikebGKGzto1k dJqQ== X-Received: by 10.52.156.100 with SMTP id wd4mr3766936vdb.39.1412947599729; Fri, 10 Oct 2014 06:26:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.163.2 with HTTP; Fri, 10 Oct 2014 06:26:18 -0700 (PDT) In-Reply-To: <1065A2D3-E37E-4C9A-A561-BB8369AC48AC@codepuppy.com> References: <1065A2D3-E37E-4C9A-A561-BB8369AC48AC@codepuppy.com> From: Alexander Shraer Date: Fri, 10 Oct 2014 06:26:18 -0700 Message-ID: Subject: Re: Changing leader to follower? To: "user@zookeeper.apache.org" Cc: "zookeeper-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7b5d2eb6c4a7fe0505117f86 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5d2eb6c4a7fe0505117f86 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I don't think there's a direct way, although this seems a useful thing to add. One think you could do is to issue a reconfig changing the leader's leading/quorum port (through which it talks with the followers). This will cause it to give up leadership while keeping it in the cluster. Cheers, Alex On Fri, Oct 10, 2014 at 5:57 AM, Jeff Potter < jpotter-zookeeper@codepuppy.com> wrote: > > Hi, > > Is there a way to =E2=80=9Cretire=E2=80=9D a leader while keeping it in t= he cluster? > > Thanks, > Jeff --047d7b5d2eb6c4a7fe0505117f86--