HBASE-1137 Add not on xceivers count to overview documentation
git-svn-id: https://svn.apache.org/repos/asf/hadoop/hbase/trunk@735783 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
029b37eade
commit
9e33297f7e
|
@ -226,6 +226,7 @@ Release 0.19.0 - Unreleased
|
|||
(Michael Gottesman via Stack)
|
||||
HBASE-1082 Administrative functions for table/region maintenance
|
||||
HBASE-1090 Atomic Check And Save in HTable (Michael Gottesman via Stack)
|
||||
HBASE-1137 Add not on xceivers count to overview documentation
|
||||
|
||||
NEW FEATURES
|
||||
HBASE-875 Use MurmurHash instead of JenkinsHash [in bloomfilters]
|
||||
|
|
|
@ -39,7 +39,11 @@
|
|||
1024 on *nix systems is insufficient if you are loading any significant
|
||||
amount of data into regionservers. See the
|
||||
<a href="http://wiki.apache.org/hadoop/Hbase/FAQ#6">FAQ: Why do I see "java.io.IOException...(Too many open files)" in my logs?</a>
|
||||
for how to up the limit.</li>
|
||||
for how to up the limit. Also, as of 0.18.x hadoop, datanodes have an upper-bound
|
||||
on the number of threads they will support (<code>dfs.datanode.max.xcievers</code>).
|
||||
Default is 256. If loading lots of data into hbase, up this limit on your
|
||||
hadoop cluster. Also consider upping the number of datanode handlers from
|
||||
the default of 3. See <code>dfs.datanode.handler.count</code>.</li>
|
||||
<li>The clocks on cluster members should be in basic alignments. Some skew is tolerable but
|
||||
wild skew can generate odd behaviors. Run <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">NTP</a>
|
||||
on your cluster, or an equivalent.</li>
|
||||
|
|
Loading…
Reference in New Issue