hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject svn commit: r832534 - /hadoop/hbase/branches/0.20/src/java/overview.html
Date Tue, 03 Nov 2009 20:11:36 GMT
Author: stack
Date: Tue Nov  3 20:11:36 2009
New Revision: 832534

URL: http://svn.apache.org/viewvc?rev=832534&view=rev
Log:
HBASE-1953 Overhaul of overview.html (html fixes, typos, consistency) - no content changes

Modified:
    hadoop/hbase/branches/0.20/src/java/overview.html

Modified: hadoop/hbase/branches/0.20/src/java/overview.html
URL: http://svn.apache.org/viewvc/hadoop/hbase/branches/0.20/src/java/overview.html?rev=832534&r1=832533&r2=832534&view=diff
==============================================================================
--- hadoop/hbase/branches/0.20/src/java/overview.html (original)
+++ hadoop/hbase/branches/0.20/src/java/overview.html Tue Nov  3 20:11:36 2009
@@ -89,6 +89,12 @@
   </li>
   <li>This is the current list of patches we recommend you apply to your running Hadoop
cluster:
     <ul>
+      <li><a hef="https://issues.apache.org/jira/browse/HADOOP-4681">HADOOP-4681/HDFS-127
<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".
+      The hadoop version bundled with hbase has this patch applied.  Its an HDFS client
+      fix so this should do for usual usage but if your cluster is missing the patch,
+      and in particular if calling hbase from a mapreduce job, you may run into this
+      issue.  If running with hadoop 0.20.2, it has this patch in place already.
+      </li>
       <li>
         <a href="https://issues.apache.org/jira/browse/HDFS-630">HDFS-630: <em>"In
DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating
the next block"</em></a>.
         Dead DataNodes take ten minutes to timeout at NameNode.



Mime
View raw message