zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asta, Greg" <greg.a...@omnigon.com>
Subject RE: Leader election in zookeeper
Date Thu, 14 Aug 2014 20:03:35 GMT
Zookeeper has properties that make it good at these tasks.  It's designed specifically for
these things.  Many other scenarios I've seen in the past were not really 'built for these
activities' but instead - had these activities tacked onto something else that was maybe less
than ideal.  Here's a few examples of where Zookeeper is "custom fit" for these activities:

- Automatic handling of disconnected clients (ephemeral nodes)
- Automatic failover and redundancy
- Callbacks that trigger real time on updates to watched nodes
- Data consistency/integrity on every server in the cluster - including 'counters' that are
accurate across every node in the cluster

>From those basic features you can construct the more complicated functionality that people
want like distributed locking and distributed "atomic" counters - in a fairly cheap and reliable
fashion.

Now - you can build all those things yourself and you can make them work on some of the more
traditional database tools as well but with varying degrees of labor.  For the users of Zookeeper
- it's really avoiding that labor and headaches that drives them to use a product like this.

-Greg

-----Original Message-----
From: mufc_fan [mailto:rajeshkumarit8292@gmail.com] 
Sent: Thursday, August 14, 2014 12:02 AM
To: zookeeper-user@hadoop.apache.org
Subject: Re: Leader election in zookeeper

can u tell me why we go for zookeeper...Before zookeeper also companies used distributed environment
in which services like leader election,lock and others are implemented and they works fine.
why we go for zookeeper?



--
View this message in context: http://zookeeper-user.578899.n2.nabble.com/Leader-election-in-zookeeper-tp7580147p7580157.html
Sent from the zookeeper-user mailing list archive at Nabble.com.

Mime
View raw message