Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

hbase-5397. performance.xml, configuration.xml - correction to ZK config. 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1245199 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2012-02-16 21:56:57 +00:00
parent 628e5cd9f2
commit b45071a8d0
2 changed files with 16 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/docbkx/configuration.xml
View File

@ -659,9 +659,16 @@ stopping hbase...............</programlisting> Shutdown can take a moment to
only but in production it is recommended that you run a only but in production it is recommended that you run a
ZooKeeper ensemble of 3, 5 or 7 machines; the more members an ZooKeeper ensemble of 3, 5 or 7 machines; the more members an
ensemble has, the more tolerant the ensemble is of host ensemble has, the more tolerant the ensemble is of host
failures. Also, run an odd number of machines. There can be no failures. Also, run an odd number of machines. In ZooKeeper,
quorum if the number of members is an even number. Give each an even number of peers is supported, but it is normally not used
ZooKeeper server around 1GB of RAM, and if possible, its own because an even sized ensemble requires, proportionally, more peers
to form a quorum than an odd sized ensemble requires. For example, an
ensemble with 4 peers requires 3 to form a quorum, while an ensemble with
5 also requires 3 to form a quorum. Thus, an ensemble of 5 allows 2 peers to
fail, and thus is more fault tolerant than the ensemble of 4, which allows
only 1 down peer.
</para>
<para>Give each ZooKeeper server around 1GB of RAM, and if possible, its own
dedicated disk (A dedicated disk is the best thing you can do dedicated disk (A dedicated disk is the best thing you can do
to ensure a performant ZooKeeper ensemble). For very heavily to ensure a performant ZooKeeper ensemble). For very heavily
loaded clusters, run ZooKeeper servers on separate machines loaded clusters, run ZooKeeper servers on separate machines

7
src/docbkx/performance.xml
View File

@ -188,7 +188,12 @@
</section> </section>
</section> </section>
<section xml:id="perf.zookeeper">
<title>ZooKeeper</title>
<para>See <xref linkend="zookeeper"/> for information on configuring ZooKeeper, and see the part
about having a dedicated disk.
</para>
</section>
<section xml:id="perf.schema"> <section xml:id="perf.schema">
<title>Schema Design</title> <title>Schema Design</title>