Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 sasi.jarch@gmail.com does not designate 216.139.236.26 as permitted sender)
Date: Mon, 7 Jul 2014 18:39:30 -0700 (PDT)
From: Sasi <sasi.jarch@gmail.com>
To: zookeeper-user@hadoop.apache.org
Message-ID: <1404783570228-7580099.post@n2.nabble.com>
Subject: Can a zookeeper client be made to influence the client-to-server
 heartbeats?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

In distributed systems that uses Apache Zookeeper for co-ordination, each
component is a client to the Zookeeper server, and it instantiates a
zookeeper instance, which in the background is sending heartbeats to the
zookeeper server. I understand that the time interval for heartbeat
communication is configurable. In situations when the "component" itself
goes into a "faulty" state but the "heartbeats" to zookeeper is good and
unaffected, proper state of this component is not communicated to the rest
of the components in the system.

Is it possible out of the box, to influence the heartbeat mechanism -
typically by passing a "status reporting function" to the zookeeper instance
- to "validate" the status of the component before sending the heartbeat ?


--
View this message in context: http://zookeeper-user.578899.n2.nabble.com/Can-a-zookeeper-client-be-made-to-influence-the-client-to-server-heartbeats-tp7580099.html
Sent from the zookeeper-user mailing list archive at Nabble.com.