zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Koert Kuipers <ko...@tresata.com>
Subject zookeeper ensemble with hbase (versus single node)
Date Fri, 11 Nov 2011 15:15:42 GMT
in various places i have read that in production one should really have a
zookeeper ensemble (with an odd number of members) as opposed to a single
zookeeper. this was also mentioned for example in the base documentation.
however, if your cluster has a single machine with namenode, secondary
namenode and hbase master, what is the benefit of having a zookeeper
cluster? if that one machine goes down your hbase isn't doing anything
anyhow, so why even bother running a zookeeper ensemble in this case? why
not just use a single zookeeper?

are the performance benefits a reason to run a zookeeper ensemble even in
this scenario? (faster reads perhaps)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message