Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
MIME-Version: 1.0
From: Jens Rantil <jens.rantil@tink.se>
Date: Mon, 23 Nov 2015 13:49:16 +0100
Message-ID: 
 <CAL+ArfWsU99PUHr5C-ZSU+b0tBD5i8ykk_Cvq7vs8R9CfDS+bQ@mail.gmail.com>
Subject: Reelection takes a long time
To: "<user@zookeeper.apache.org>" <user@zookeeper.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c0b74c650de48052534a8b4

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

Hi,

*Problem:* We are running a Zookeeper ensemble that takes a bit too long
time before a new master is elected when the old one is brought down.

*Question:* Which configuration settings do I need to change to decrease
the time before a reelection occurs? tickTime and syncLimit?

*Additionals:* The relevant (I think!) configuration we are running is:

# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=60
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=30

I have previously increases the limits somewhat to accomodate for zookeeper
nodes not being able to come up due to too large snapshot. This could
definitely be the reason why reelection takes longer time.

Any input appreciated.

Cheers,
Jens

-- 
Jens Rantil
Backend engineer
Tink AB

Email: jens.rantil@tink.se
Phone: +46 708 84 18 32
Web: www.tink.se

Facebook <https://www.facebook.com/#!/tink.se> Linkedin
<http://www.linkedin.com/company/2735919?trk=vsrp_companies_res_photo&trkInfo=VSRPsearchId%3A1057023381369207406670%2CVSRPtargetId%3A2735919%2CVSRPcmpt%3Aprimary>
 Twitter <https://twitter.com/tink>

--94eb2c0b74c650de48052534a8b4--