accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r956087 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.3.html
Date Fri, 26 Jun 2015 18:04:46 GMT
Author: buildbot
Date: Fri Jun 26 18:04:45 2015
New Revision: 956087

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 Fri Jun 26 18:04:45 2015
@@ -1 +1 @@

Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.3.html
--- websites/staging/accumulo/trunk/content/release_notes/1.5.3.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.5.3.html Fri Jun 26 18:04:45 2015
@@ -213,23 +213,25 @@ Latest 1.5 release: <strong>1.5.3</stron
     <h1 class="title">Apache Accumulo 1.5.3 Release Notes</h1>
-    <p>Apache Accumulo 1.5.3 is a bug-fix release for the 1.5 series. It is likely
the last
-release in this line due to lack of user interest and the magnitude of improvements
-in newer release lines.</p>
+    <p>Apache Accumulo 1.5.3 is a bug-fix release for the 1.5 series. It is likely
to be the last
+1.5 release, with development shifting towards newer release lines. We recommend upgrading
+to a newer version to continue to get bug fixes and new features.</p>
 <p>In the context of Accumulo's <a href="">Semantic Versioning</a>
<a href="">guidelines</a>,
-this is a "patch version". This means that there have been no API changes. Any
+this is a "patch version". This means that there should be no public API changes. Any
 changes which were made were done in a backwards-compatible manner. Code that
-runs against 1.5.2 is guaranteed to run against 1.5.3.</p>
+runs against 1.5.2 should run against 1.5.3.</p>
+<p>Previous release notes for 1.5.2 can be found <a href="/release_notes/1.5.2.html">here</a>.</p>
 <p>We'd like to thank all of the committers and contributors which had a part in
-making this release from code contributions to testing. Everyone's efforts are
+making this release, from code contributions to testing. Everyone's efforts are
 greatly appreciated.</p>
-<h1 id="security-changes">Security Changes</h1>
-<h2 id="sslv3-disabled-poodle">SSLv3 disabled (POODLE)</h2>
+<h2 id="security-changes">Security Changes</h2>
+<h3 id="sslv3-disabled-poodle"><a href="">SSLv3
disabled (POODLE)</a></h3>
 <p>Many Accumulo services were capable of enabling wire encryption using
-SSL connectors. 1.5.3 disables the problematic SSLv3 version which was
-susceptible to the man-in-the-middle attack.</p>
-<h1 id="notable-bug-fixes">Notable Bug Fixes</h1>
-<h2 id="sourceswitchingiterator-deadlock">SourceSwitchingIterator Deadlock</h2>
+SSL connectors. To be safe, <a href="">ACCUMULO-3316</a>
disables the problematic SSLv3 version by default which was
+potentially susceptible to the man-in-the-middle attack. [ACCUMULO-3317] also disables SSLv3
in the monitor,
+so it will not accept SSLv3 client connections, when running it with https.</p>
+<h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
+<h3 id="sourceswitchingiterator-deadlock"><a href="">SourceSwitchingIterator
 <p>An instance of SourceSwitchingIterator, the Accumulo iterator which transparently
 whether data for a tablet read from memory (the in-memory map) or disk (HDFS after a minor
 compaction), was found deadlocked in a production system.</p>
@@ -237,7 +239,7 @@ compaction), was found deadlocked in a p
 without restarting the tablet server. ACCUMULO-3745 fixes the inconsistent synchronization
 inside of the SourceSwitchingIterator to prevent this deadlock from happening in the future.</p>
 <p>The only mitigation of this bug was to restart the tablet server that is deadlocked.</p>
-<h2 id="table-flush-blocked-indefinitely">Table flush blocked indefinitely</h2>
+<h3 id="table-flush-blocked-indefinitely"><a href="">Table
flush blocked indefinitely</a></h3>
 <p>While running the Accumulo RandomWalk distributed test, it was observed that all
activity in
 Accumulo had stopped and there was an offline Accumulo metadata table tablet. The system
 tried to flush a user tablet, but the metadata table was not online (likely due to the agitation
@@ -253,16 +255,18 @@ message requesting a metadata tablet to
 because the number of metadata tablets is typically very small with respect to the total
number of
 tablets in the system.</p>
 <p>The only mitigation of this bug was to restart the tablet server that is hung.</p>
-<h2 id="rpc-connections-not-cached">RPC Connections not cached</h2>
+<h3 id="rpc-connections-not-cached"><a href="">RPC
Connections not cached</a></h3>
 <p>It was observed that the underlying connection for invoking RPCs were not actually
being cached,
 despite it being requested that they should be cached. While this did not result in a noticed
 performance impact, it was deficiency. <a href="">ACCUMULO-3574</a>
ensures that connections are cached when
 it is requested that they are.</p>
-<h2 id="deletes-on-thrift-proxy-api-ignored">Deletes on Thrift Proxy API ignored</h2>
+<h3 id="deletes-on-thrift-proxy-api-ignored"><a href="">Deletes
on Thrift Proxy API ignored</a></h3>
 <p>A user noted that when trying to specify a delete using the Accumulo Thrift Proxy,
the delete
 was treated as an update. <a href="">ACCUMULO-3474</a>
fixes the Proxy server such that deletes are properly
 respected as specified by the client.</p>
-<h1 id="testing">Testing</h1>
+<h2 id="other-changes">Other Changes</h2>
+<p>Other changes for this version can be found <a href="">in
+<h2 id="testing">Testing</h2>
 <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
 randomly restarting Accumulo processes and Hadoop DataNode processes, and, in

View raw message