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

HBASE-1573 Holes in master state change; updated startcode and server go into .META. but catalog scanner just got old values 

git-svn-id: https://svn.apache.org/repos/asf/hadoop/hbase/trunk@795916 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2009-07-20 16:55:17 +00:00
parent 8809929dff
commit b740d37d0b
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/java/overview.html
View File

@ -50,11 +50,13 @@
<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. Also, as of 0.18.x hadoop, datanodes have an upper-bound 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>). 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 Default is 256. Up this limit on your hadoop cluster.
hadoop cluster.
<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>
<li>HBase servers put up 10 listeners for incoming connections by default. Up this
number if you have a dataset of any substance by setting hbase.regionserver.handler.count
in your hbase-site.xml.</li>
<li>This is a list of patches we recommend you apply to your running Hadoop cluster: <li>This is a list of patches we recommend you apply to your running Hadoop cluster:
<ul> <ul>
<li><a hef="https://issues.apache.org/jira/browse/HADOOP-4681">HADOOP-4681 <i>"DFSClient block read failures cause open DFSInputStream to become unusable"</i></a>. This patch will help with the ever-popular, "No live nodes contain current block". <li><a hef="https://issues.apache.org/jira/browse/HADOOP-4681">HADOOP-4681 <i>"DFSClient block read failures cause open DFSInputStream to become unusable"</i></a>. This patch will help with the ever-popular, "No live nodes contain current block".