You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by bu...@apache.org on 2015/09/06 00:15:58 UTC
svn commit: r964492 - in /websites/staging/accumulo/trunk/content: ./
release_notes/1.5.4.html
Author: buildbot
Date: Sat Sep 5 22:15:58 2015
New Revision: 964492
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/release_notes/1.5.4.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Sep 5 22:15:58 2015
@@ -1 +1 @@
-1701428
+1701429
Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.4.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.5.4.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.5.4.html Sat Sep 5 22:15:58 2015
@@ -264,14 +264,6 @@ that were added) are described in <a hre
and Continuous Ingest tests run on any number of nodes. <em>Agitation</em> refers to
randomly restarting Accumulo processes and Hadoop DataNode processes, and, in
HDFS High-Availability instances, forcing NameNode fail-over.</p>
-<p>During testing, multiple Accumulo developers noticed some stability issues
-with HDFS using Apache Hadoop 2.6.0 when restarting Accumulo processes and
-HDFS datanodes. The developers investigated these issues as a part of the
-normal release testing procedures, but were unable to find a definitive cause
-of these failures. Users are encouraged to follow
-[ACCUMULO-2388][ACCUMULO-2388] if they wish to follow any future developments.
-One possible workaround is to increase the <code>general.rpc.timeout</code> in the
-Accumulo configuration from <code>120s</code> to <code>240s</code>.</p>
<table id="release_notes_testing">
<tr>
<th>OS</th>