Author: buildbot
Date: Thu Feb 18 00:05:04 2016
New Revision: 980667

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 18 00:05:04 2016
@@ -1 +1 @@
-1730977
+1730984

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 Thu Feb 18 
00:05:04 2016
@@ -266,9 +266,9 @@ be blocked until the Accumulo Master pro
 <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 
link">&para;</a></h3>
 <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.
+where a special RPC (a "oneway" call) would leave unwanted data on the 
underlying
+Thrift connection. After this extra data was left on connection, all 
subsequent RPCs
+re-using that connection would fail with "out of sequence response" error 
messages.
 Accumulo would be left in a bad state until the mishandled connections were 
released
 or Accumulo services were restarted. (<a 
href="https://issues.apache.org/jira/browse/ACCUMULO-4065";>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>


Reply via email to