hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "ZooKeeper/SoC2010Ideas" by HenryRobinson
Date Fri, 12 Mar 2010 23:56:46 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "ZooKeeper/SoC2010Ideas" page has been changed by HenryRobinson.
http://wiki.apache.org/hadoop/ZooKeeper/SoC2010Ideas?action=diff&rev1=3&rev2=4

--------------------------------------------------

  ==== Requirements ====
  Java, some networking familiarity
  ==== Description ====
- ZK 3.3.0 added [[http://www.cloudera.com/blog/2009/12/observers-making-zookeeper-scale-even-further/|''observers'']
which are non-voting members of a ZK ensemble. One use case for observers is as a proxy to
a remote voting ensemble, say in a different data center. Since observers do not need to vote,
there are less strict latency requirements on the delivery of messages to them. WAN traffic
is also expensive. This project would investigate and implement batching of messages to observers,
and potential mechanisms for decreasing the number of messages that need to be sent. For example,
a destructive update to a znode twice in a row does not theoretically need to be sent twice
- although making this work correctly with ZAB will be a challenge.  
+ ZK 3.3.0 added ''[[http://www.cloudera.com/blog/2009/12/observers-making-zookeeper-scale-even-further/|observers]''
which are non-voting members of a ZK ensemble. One use case for observers is as a proxy to
a remote voting ensemble, say in a different data center. Since observers do not need to vote,
there are less strict latency requirements on the delivery of messages to them. WAN traffic
is also expensive. This project would investigate and implement batching of messages to observers,
and potential mechanisms for decreasing the number of messages that need to be sent. For example,
a destructive update to a znode twice in a row does not theoretically need to be sent twice
- although making this work correctly with ZAB will be a challenge.  
  ----
  === FUSE module for BookKeeper ===
  ==== Possible Mentor ====

Mime
View raw message