diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml index b1bc71e9a6d..069b50f0c63 100644 --- a/src/docbkx/book.xml +++ b/src/docbkx/book.xml @@ -91,7 +91,11 @@ Here is a quick guide to starting up a standalone HBase instance, creating a table and inserting rows into a table via the HBase Shell, and then cleaning up and shutting - down your running instance. + down your running instance. + + Be warned that the HBase started using these + instructions is for play only. See the next section for how to + set up a non-toy HBase deploy. Download and unpack the latest stable release. @@ -217,13 +221,12 @@ hbase(main):013:0> drop 'test' $ ./bin/stop-hbase.sh stopping hbase............... - - To learn how to set up a HBase in distributed mode, see the next section. + +
Not-so-quick Start - The HBase API overview document contains a detailed Getting Started with a list of requirements and description of the @@ -237,6 +240,13 @@ stopping hbase............... Configuration + HBase uses the same configuration system as Hadoop. + To configure a deploy, edit a file of environment variables + in conf/hbase-env.sh -- this configuration + is used mostly by the launcher shell scripts getting the cluster + off the ground -- and then add configuration to an xml file to + do things like override HBase defaults, tell HBase what Filesystem to + use, and the location of the ZooKeeper ensemble.
@@ -277,7 +287,8 @@ stopping hbase...............
Required Configurations Here are some configurations you must configure to suit - your deploy. + your deploy. Failure to do so will almost certainly result in + data loss.
<varname>ulimit</varname> @@ -290,7 +301,10 @@ stopping hbase............... 2010-04-06 03:04:37,542 INFO org.apache.hadoop.hdfs.DFSClient: Abandoning block blk_-6935524980745310745_1391901 Do yourself a favor and change the upper bound on the number of file descriptors. - Set it to north of 10k. See the above referenced FAQ for how. + Set it to north of 10k. See the above referenced FAQ for how. Verify this change + has taken effect by checking the first line in your HBase logs. It'll print out + the ulimit available to the running process (A frequent mistake is upping the ulimit + for a user other than the user running the HBase process). To be clear, upping the file descriptors for the user who is running the HBase process is an operating system configuration, not an HBase configuration. @@ -309,6 +323,13 @@ stopping hbase............... <value>2047</value> </property> + + + For background see + Problem: "xceiverCount 258 exceeds the limit of concurrent xcievers 256". + + +
@@ -337,8 +358,6 @@ stopping hbase...............
- -