Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of german.blanco.blanco@gmail.com
 designates 209.85.223.194 as permitted sender)
MIME-Version: 1.0
Date: Tue, 16 Apr 2013 13:32:23 +0200
Message-ID: 
 <CAEH-zfo2EbXKuiHrRx61ptw6uQ7irwnBSxa89XiJubD_gpkTXg@mail.gmail.com>
Subject: timeout per transaction?
From: German Blanco <german.blanco.blanco@gmail.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=14dae93404451c584304da78b94b

--14dae93404451c584304da78b94b
Content-Type: text/plain; charset=ISO-8859-1

Hello,

According to the System Administrator's Guide:
syncTime -> Amount of time, in ticks (see
tickTime<http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#id_tickTime>),
to allow followers to sync with ZooKeeper. If followers fall too far behind
a leader, they will be dropped.

In order to check what is the time or number of transactions that a
follower may fall behind, I did some tests. I couldn't find a way to make a
transaction timeout in the Leader. It seems that the Leader adds
transactions to the list of outstanding proposals and they stay there until
a commit arrives or otherwise forever.

As long as Followers respond to the sync request, the quorum keeps running.

Is this really the behaviour? What is then the way in which it is
guaranteed that followers do not "fall too far behind a leader"?

Thanks in advance for your help.

--14dae93404451c584304da78b94b--