Author: buildbot
Date: Sat Sep 5 22:15:06 2015
New Revision: 964491
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:06 2015
@@ -1 +1 @@
-1701425
+1701428
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:06 2015
@@ -34,7 +34,7 @@
<script src="/js/dataTables.bootstrap.js"></script>
<link href="/css/accumulo.css" rel="stylesheet" type="text/css">
<link
href="//netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css"
rel="stylesheet">
- <title>Apache Accumulo 1.5.3 Release Notes</title>
+ <title>Apache Accumulo 1.5.4 Release Notes</title>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -216,7 +216,7 @@ Latest 1.5 release: <strong>1.5.3</stron
<div id="content">
- <h1 class="title">Apache Accumulo 1.5.3 Release Notes</h1>
+ <h1 class="title">Apache Accumulo 1.5.4 Release Notes</h1>
<style type="text/css">
/* The following code is added by mdx_elementid.py
@@ -229,58 +229,36 @@ Latest 1.5 release: <strong>1.5.3</stron
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
-<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="http://semver.org";>Semantic
Versioning</a> <a
href="https://github.com/apache/accumulo/blob/1.7.0/README.md#api";>guidelines</a>,
-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 should run against 1.5.3.</p>
+<p>Apache Accumulo 1.5.4 is one more bug-fix release for the 1.5 series. Like
1.5.3 before it, this release contains a
+very small changeset when considering the normal size of changes in a
release.</p>
+<p>This release contains no changes to the <a
href="https://github.com/apache/accumulo/blob/1.7.0/README.md#api";>public
API</a>. As such, there are no concerns
+for the compatibility of user code running against 1.5.3. All users are
encourage to upgrade
+immediately without concern of stability and compatibility.</p>
+<p>A full list of changes is available via <a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312121&version=12333106";>CHANGES</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
greatly appreciated.</p>
-<h2 id="security-changes">Security Changes<a class="headerlink"
href="#security-changes" title="Permanent link">¶</a></h2>
-<h3 id="sslv3-disabled-poodle"><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3316";>SSLv3 disabled
(POODLE)</a><a class="headerlink" href="#sslv3-disabled-poodle"
title="Permanent link">¶</a></h3>
-<p>Many Accumulo services were capable of enabling wire encryption using
-SSL connectors. To be safe, <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3316";>ACCUMULO-3316</a>
disables the problematic SSLv3 version by default which was
-potentially susceptible to the man-in-the-middle attack. <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3317";>ACCUMULO-3317</a>
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<a class="headerlink"
href="#notable-bug-fixes" title="Permanent link">¶</a></h2>
-<h3 id="sourceswitchingiterator-deadlock"><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3745";>SourceSwitchingIterator
Deadlock</a><a class="headerlink" href="#sourceswitchingiterator-deadlock"
title="Permanent link">¶</a></h3>
-<p>An instance of SourceSwitchingIterator, the Accumulo iterator which
transparently manages
-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>
-<p>This deadlock prevented the scan and the minor compaction from ever
successfully completing
-without restarting the tablet server. <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3745";>ACCUMULO-3745</a>
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>
-<h3 id="table-flush-blocked-indefinitely"><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3597";>Table flush blocked
indefinitely</a><a class="headerlink" href="#table-flush-blocked-indefinitely"
title="Permanent link">¶</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 first
-tried to flush a user tablet, but the metadata table was not online (likely
due to the agitation
-process which stops and starts Accumulo processes during the test). After this
call, a call to
-load the metadata tablet was queued but could not complete until the previous
flush call. Thus,
-a deadlock occurred.</p>
-<p>This deadlock happened because the synchronous flush call could not
complete before the load
-tablet call completed, but the load tablet call couldn't run because of
connection caching we
-perform in Accumulo's RPC layer to reduce the quantity of sockets we need to
create to send data.
-<a
href="https://issues.apache.org/jira/browse/ACCUMULO-3597";>ACCUMULO-3597</a>
prevents this deadlock by forcing the use of a non-cached connection for the RPC
-message requesting a metadata tablet to be loaded.</p>
-<p>While this feature does result in additional network resources to be used,
the concern is minimal
-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>
-<h3 id="rpc-connections-not-cached"><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3574";>RPC Connections not
cached</a><a class="headerlink" href="#rpc-connections-not-cached"
title="Permanent link">¶</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="https://issues.apache.org/jira/browse/ACCUMULO-3574";>ACCUMULO-3574</a>
ensures that connections are cached when
-it is requested that they are.</p>
-<h3 id="deletes-on-thrift-proxy-api-ignored"><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3474";>Deletes on Thrift
Proxy API ignored</a><a class="headerlink"
href="#deletes-on-thrift-proxy-api-ignored" title="Permanent
link">¶</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="https://issues.apache.org/jira/browse/ACCUMULO-3474";>ACCUMULO-3474</a>
fixes the Proxy server such that deletes are properly
-respected as specified by the client.</p>
-<h2 id="other-changes">Other Changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
-<p>Other changes for this version can be found <a
href="https://issues.apache.org/jira/browse/ACCUMULO/fixforversion/12328662";>in
JIRA</a>.</p>
+<h2 id="correctness-bugs">Correctness Bugs<a class="headerlink"
href="#correctness-bugs" title="Permanent link">¶</a></h2>
+<h3 id="silent-data-loss-via-bulk-imported-files">Silent data-loss via bulk
imported files<a class="headerlink"
href="#silent-data-loss-via-bulk-imported-files" title="Permanent
link">¶</a></h3>
+<p>A user recently reported that a simple bulk-import application would
occasionally lose some records. Through investigation,
+it was found that when bulk imports into a table failed the initial
assignment, the logic that automatically retries
+the imports was incorrectly choosing the tablets to import the files into. <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3967";>ACCUMULO-3967</a>
contains
+more information on the cause and identification of the bug. The data-loss
condition would only affect entire files.
+If records from a file exist in Accumulo, it is still guaranteed that all
records within that imported file were
+successful.</p>
+<p>As such, users who have bulk import applications using previous versions of
Accumulo should verify that all of their
+data was correctly ingested into Accumulo and immediately update to Accumulo
1.5.4.</p>
+<p>Thanks to Edward Seidl for reporting this bug to us!</p>
+<h2 id="server-side-auditing-changes">Server-side auditing changes<a
class="headerlink" href="#server-side-auditing-changes" title="Permanent
link">¶</a></h2>
+<p>Thanks to James Mello for reporting and providing the fixes to the
following server-side auditing issues.</p>
+<h3 id="incorrect-audit-initialization">Incorrect audit initialization<a
class="headerlink" href="#incorrect-audit-initialization" title="Permanent
link">¶</a></h3>
+<p>It was observed that the implementation used to audit user API requests on
Accumulo server processes
+was not being correctly initialized which caused audit messages to never be
generated. This was rectified
+in <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3939";>ACCUMULO-3939</a>.</p>
+<h3 id="missing-audit-implementations">Missing audit implementations<a
class="headerlink" href="#missing-audit-implementations" title="Permanent
link">¶</a></h3>
+<p>It was also observed that some server-side API implementations did not
include audit messages which resulted
+in an incomplete historical picture on what operations a user might have
invoked. The missing audits (and those
+that were added) are described in <a
href="https://issues.apache.org/jira/browse/ACCUMULO-3946";>ACCUMULO-3946</a>.</p>
<h2 id="testing">Testing<a class="headerlink" href="#testing" title="Permanent
link">¶</a></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 to
@@ -291,7 +269,7 @@ with HDFS using Apache Hadoop 2.6.0 when
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.
+[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">
@@ -304,12 +282,12 @@ Accumulo configuration from <code>120s</
<th>Tests</th>
</tr>
<tr>
- <td>Gentoo</tdt>
+ <td>OSX</tdt>
<td>2.6.0</td>
<td>1</td>
<td>3.4.5</td>
<td>No</td>
- <td>Unit and Integration Tests</td>
+ <td>Unit and Functional Tests</td>
</tr>
<tr>
<td>Centos 6.5</tdt>
@@ -317,7 +295,7 @@ Accumulo configuration from <code>120s</
<td>6</td>
<td>3.4.5</td>
<td>No</td>
- <td>Continuous Ingest and Verify</td>
+ <td>Continuous Ingest and Verify (10B entries), Randomwalk (24hrs)</td>
</tr>
</table>
</div>
