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

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:
Michael Stack 2009-01-19 19:46:50 +00:00
parent 029b37eade
commit 9e33297f7e
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGES.txt
View File

@ -226,6 +226,7 @@ Release 0.19.0 - Unreleased
(Michael Gottesman via Stack) (Michael Gottesman via Stack)
HBASE-1082 Administrative functions for table/region maintenance HBASE-1082 Administrative functions for table/region maintenance
HBASE-1090 Atomic Check And Save in HTable (Michael Gottesman via Stack) HBASE-1090 Atomic Check And Save in HTable (Michael Gottesman via Stack)
HBASE-1137 Add not on xceivers count to overview documentation
NEW FEATURES NEW FEATURES
HBASE-875 Use MurmurHash instead of JenkinsHash [in bloomfilters] HBASE-875 Use MurmurHash instead of JenkinsHash [in bloomfilters]

6
src/java/overview.html
View File

@ -39,7 +39,11 @@
1024 on *nix systems is insufficient if you are loading any significant 1024 on *nix systems is insufficient if you are loading any significant
amount of data into regionservers. See the 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> <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 <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> 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> on your cluster, or an equivalent.</li>