accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r979999 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.5.html
Date Wed, 10 Feb 2016 05:34:52 GMT
Author: buildbot
Date: Wed Feb 10 05:34:52 2016
New Revision: 979999

Staging update by buildbot for accumulo

    websites/staging/accumulo/trunk/content/   (props changed)

Propchange: websites/staging/accumulo/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 10 05:34:52 2016
@@ -1 +1 @@

Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.5.html
--- websites/staging/accumulo/trunk/content/release_notes/1.6.5.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.5.html Wed Feb 10 05:34:52 2016
@@ -251,13 +251,28 @@ it from running to completion entirely.
 ACCUMULO_CLIENT_CONF_PATH, and improved the detection of the client.conf file if
 ACCUMULO_CLIENT_CONF_PATH was set to a directory containing client.conf.
 (<a href="">ACCUMULO-4026</a>,<a
+<h3 id="transient-zookeeper-disconnect-causes-fate-threads-to-exit">Transient ZooKeeper
disconnect causes FATE threads to exit<a class="headerlink" href="#transient-zookeeper-disconnect-causes-fate-threads-to-exit"
title="Permanent link">&para;</a></h3>
+<p>ZooKeeper clients are expected to handle the situation where they become
+disconnected from the ZooKeeper server and must wait to be reconnected
+before continuing ZooKeeper operations.</p>
+<p>The dedicated threads running inside the Accumulo Master process for FATE
+actions had the potential unexpectedly exit in this disconnected state.
+This caused a scenario where all future FATE-based operations would
+be blocked until the Accumulo Master process was restarted. (<a href="">ACCUMULO-4060</a>)</p>
+<h3 id="incorrect-management-of-certain-thrift-rpcs">Incorrect management of certain
Thrift RPCs<a class="headerlink" href="#incorrect-management-of-certain-thrift-rpcs" title="Permanent
+<p>Accumulo relies on Apache Thrift to implement remote procedure calls between
+Accumulo services. Accumulo's use of Thrift uncovered an unfortunate situation
+where this special RPC (a "oneway" call) would leave unwanted data on the underlying
+Thrift connection. After this extra was left on connection, all subsequent RPCs
+re-using that connection would fail with "out of sequence reponse" error messages.
+Accumulo would be left in a bad state until the mishandled connections were released
+or Accumulo services were restarted. (<a href="">ACCUMULO-4065</a>)</p>
 <h2 id="other-notable-changes">Other Notable Changes<a class="headerlink" href="#other-notable-changes"
title="Permanent link">&para;</a></h2>
 <li><a href="">ACCUMULO-3509</a>
Fixed some lock contention in TabletServer, preventing resource cleanup</li>
 <li><a href="">ACCUMULO-3734</a>
Fixed quote-escaping bug in VisibilityConstraint</li>
 <li><a href="">ACCUMULO-4025</a>
Fixed cleanup of bulk load fate transactions</li>
-<li><a href="">ACCUMULO-4065</a>
Worked around buggy thrift behavior with oneway methods</li>
-<li><a href="">ACCUMULO-4070</a>
Fixed Kerberos renewal</li>
+<li><a href="">ACCUMULO-4070</a>
Fixed Kerberos ticket renewal for all Accumulo services</li>
 <li><a href="">ACCUMULO-4098</a>,<a
href="">ACCUMULO-4113</a> Fixed
widespread misuse of ByteBuffer</li>
 <h2 id="testing">Testing<a class="headerlink" href="#testing" title="Permanent link">&para;</a></h2>

View raw message