[
https://issues.apache.org/jira/browse/HBASE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755055#action_12755055
]
stack commented on HBASE-1755:
------------------------------
"ZooKeeper was not designed to be a general database or large object store.
Instead, it manages coordination data. This data can come in the form of
configuration, status information, rendezvous, etc. A common property of the
various forms of coordination data is that they are relatively small: measured
in kilobytes. The ZooKeeper client and the server implementations have sanity
checks to ensure that znodes have less than 1M of data, but the data should be
much less than that on average. Operating on relatively large data sizes will
cause some operations to take much more time than others and will affect the
latencies of some operations because of the extra time needed to move more data
over the network and onto storage media. If large data storage is needed, the
usually pattern of dealing with such data is to store it on a bulk storage
system, such as NFS or HDFS, and store pointers to the storage locations in
ZooKeeper."
http://hadoop.apache.org/zookeeper/docs/r3.2.1/zookeeperProgrammers.html
> Putting 'Meta' table into ZooKeeper
> -----------------------------------
>
> Key: HBASE-1755
> URL: https://issues.apache.org/jira/browse/HBASE-1755
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.21.0
> Reporter: Erik Holstad
> Fix For: 0.21.0
>
>
> Talking at the hackathon about moving the Meta table into ZooKeeper.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
