diff --git a/CHANGES.txt b/CHANGES.txt index 6905253f836..8327b1bba32 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -492,6 +492,8 @@ Release 0.21.0 - Unreleased writes occur in same millisecond (Clint Morgan via J-D) HBASE-2360 Make sure we have all the hadoop fixes in our our copy of its rpc (Todd Lipcon via Stack) + HBASE-2423 Update 'Getting Started' for 0.20.4 including making + "important configurations more visiable" NEW FEATURES HBASE-1961 HBase EC2 scripts diff --git a/core/src/main/javadoc/overview.html b/core/src/main/javadoc/overview.html index 1a762886cca..45251d90080 100644 --- a/core/src/main/javadoc/overview.html +++ b/core/src/main/javadoc/overview.html @@ -53,7 +53,7 @@
dfs.datanode.max.xcievers
). The default is 256 threads. Up this limit on your hadoop cluster.
- hbase.regionserver.handler.count
- in your hbase-site.xml
.
- +2010-04-06 03:04:37,542 INFO org.apache.hadoop.hdfs.DFSClient: Exception increateBlockOutputStream java.io.EOFException +2010-04-06 03:04:37,542 INFO org.apache.hadoop.hdfs.DFSClient: Abandoning block blk_-6935524980745310745_1391901 ++ Do yourself a favor and change this to more than 10k using the FAQ. + Also, HDFS has an upper bound of files that it can serve at the same time, called xcievers (yes, this is misspelled). Again, before doing any loading, + make sure you configured Hadoop's conf/hdfs-site.xml with this: +
+<property> + <name>dfs.datanode.max.xcievers</name> + <value>2047</value> +</property> ++ See the background of this issue here: Problem: "xceiverCount 258 exceeds the limit of concurrent xcievers 256". + Failure to follow these instructions will result in data loss. +