svn commit: r951937 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.7.0.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 19 21:59:52 2015
New Revision: 951937

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/release_notes/1.7.0.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 19 21:59:52 2015
@@ -1 +1 @@
-1680402
+1680403

Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.7.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.0.html Tue May 19 21:59:52 2015
@@ -436,6 +436,11 @@ are available is limited to the expected
 <p>Each unit and functional test only runs on a single node, while the RandomWalk 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 failover.</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 <a href="https://issues.apache.org/jira/browse/ACCUMULO-2388">ACCUMULO-2388</a> 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>