Author: buildbot
Date: Mon Feb 22 19:25:11 2016
New Revision: 980974
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/release_notes/1.7.1.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 22 19:25:11 2016
@@ -1 +1 @@
-1730996
+1731723
Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.1.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.7.1.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.1.html Mon Feb 22
19:25:11 2016
@@ -234,28 +234,55 @@ complete list.</p>
as possible to benefit from the improvements with very little concern in change
of underlying functionality. Users of 1.6 or earlier that are seeking to
upgrade to 1.7 should consider 1.7.1 as a starting point.</p>
-<h2 id="outstanding-known-issues">Outstanding Known Issues<a
class="headerlink" href="#outstanding-known-issues" title="Permanent
link">¶</a></h2>
-<p>Be aware that a small documentation bug exists with the compact command in
the
-shell ([ACCUMULO-4138][ACCUMULO-4138]). The documentation for the begin row and
-end row should be described as exclusive and inclusive, respectively, rather
-than the incorrect description of both being inclusive.</p>
<h2 id="highlights">Highlights<a class="headerlink" href="#highlights"
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.7.1 (This is the same bug that
+was fixed in 1.6.4, so you won't be affected if you're running 1.6.4 or
newer).</p>
<h3 id="queued-compactions-not-running">Queued Compactions Not Running<a
class="headerlink" href="#queued-compactions-not-running" title="Permanent
link">¶</a></h3>
-<p>Found and fixed a bug ([ACCUMULO-4016][ACCUMULO-4016]) in which some queued
+<p>Found and fixed a bug (<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4016";>ACCUMULO-4016</a>)
in which some queued
compactions would never run if the number of files changed while the tablet was
queued.</p>
+<h3 id="kerberos-ticket-renewals">Kerberos Ticket Renewals<a
class="headerlink" href="#kerberos-ticket-renewals" title="Permanent
link">¶</a></h3>
+<p>A bug was fixed which caused Accumulo clients and services to fail to check
and
+(if necessary) renew their Kerberos credentials. This would eventually lead to
+these components failing to properly authenticate until they were restarted.
+(<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4069";>ACCUMULO-4069</a>)</p>
+<h3 id="updated-commons-collection">Updated commons-collection<a
class="headerlink" href="#updated-commons-collection" title="Permanent
link">¶</a></h3>
+<p>The bundled commons-collection library was updated from version 3.2.1 to
3.2.2
+because of a reported vulnerability in that library.
+(<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4056";>ACCUMULO-4056</a>)</p>
<h3 id="faster-processing-of-conditional-mutations">Faster Processing of
Conditional Mutations<a class="headerlink"
href="#faster-processing-of-conditional-mutations" title="Permanent
link">¶</a></h3>
<p>Improved ConditionalMutation processing time by a factor of 3.
-([ACCUMULO-4066][ACCUMULO-4066])</p>
+(<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4066";>ACCUMULO-4066</a>)</p>
<h3 id="slow-gc-while-bulk-importing">Slow GC While Bulk Importing<a
class="headerlink" href="#slow-gc-while-bulk-importing" title="Permanent
link">¶</a></h3>
<p>Found and worked around an issue where lots of bulk imports creating many
new
files would significantly impair the Accumulo GC service, and possibly prevent
-it from running to completion entirely. ([ACCUMULO-4021][ACCUMULO-4021])</p>
+it from running to completion entirely. (<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4021";>ACCUMULO-4021</a>)</p>
+<h3 id="unnoticed-per-table-configuration-updates">Unnoticed Per-table
Configuration Updates<a class="headerlink"
href="#unnoticed-per-table-configuration-updates" title="Permanent
link">¶</a></h3>
+<p>Fixed a bug which caused tablet servers to not notice changes to the
per-table
+constraints, under some circumstances. (<a
href="https://issues.apache.org/jira/browse/ACCUMULO-3859";>ACCUMULO-3859</a>)</p>
+<h3 id="tabletservers-kill-themselves-on-centos7">TabletServers kill
themselves on CentOS7<a class="headerlink"
href="#tabletservers-kill-themselves-on-centos7" title="Permanent
link">¶</a></h3>
+<p>Reduced the aggressiveness with which Accumulo Tablet Servers preemptively
+killed themselves when a local filesystem switched to read-only (indicating a
+possible failure). To reduce false positives, such as those which can occur
+with systemd's extra cgroup mounts in CentOS7, an additional check was added to
+ensure that tablet servers would only kill themselves if an ext- or
+xfs-formatted disk switched to read-only. (<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4080";>ACCUMULO-4080</a>)</p>
<h3 id="improvements-in-locating-client-configuration-file">Improvements in
Locating Client Configuration File<a class="headerlink"
href="#improvements-in-locating-client-configuration-file" title="Permanent
link">¶</a></h3>
<p>Fixed some unexpected error messages related to setting
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.
-([ACCUMULO-4026][ACCUMULO-4026],[ACCUMULO-4027][ACCUMULO-4027])</p>
+(<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4026";>ACCUMULO-4026</a>,<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4027";>ACCUMULO-4027</a>)</p>
<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">¶</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
@@ -263,7 +290,7 @@ before continuing ZooKeeper operations.<
<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.
([ACCUMULO-4060][ACCUMULO-4060])</p>
+be blocked until the Accumulo Master process was restarted. (<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4060";>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
link">¶</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
@@ -271,14 +298,14 @@ where a special RPC (a "oneway" call) wo
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. ([ACCUMULO-4065][ACCUMULO-4065])</p>
+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">¶</a></h2>
<ul>
<li><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3509";>ACCUMULO-3509</a>
Fixed some lock contention in TabletServer, preventing resource cleanup</li>
-<li>[ACCUMULO-3734][ACCUMULO-3734] Fixed quote-escaping bug in
VisibilityConstraint</li>
-<li>[ACCUMULO-4025][ACCUMULO-4025] Fixed cleanup of bulk load fate
transactions</li>
-<li>[ACCUMULO-4070][ACCUMULO-4070] Fixed Kerberos ticket renewal for all
Accumulo services</li>
-<li>[ACCUMULO-4098][ACCUMULO-4098],[ACCUMULO-4113][ACCUMULO-4113] Fixed
widespread misuse of ByteBuffer</li>
+<li><a
href="https://issues.apache.org/jira/browse/ACCUMULO-3734";>ACCUMULO-3734</a>
Fixed quote-escaping bug in VisibilityConstraint</li>
+<li><a
href="https://issues.apache.org/jira/browse/ACCUMULO-4025";>ACCUMULO-4025</a>
Fixed cleanup of bulk load fate transactions</li>
+<li><a
href="https://issues.apache.org/jira/browse/ACCUMULO-4070";>ACCUMULO-4070</a>
Fixed Kerberos ticket renewal for all Accumulo services</li>
+<li><a
href="https://issues.apache.org/jira/browse/ACCUMULO-4098";>ACCUMULO-4098</a>,<a
href="https://issues.apache.org/jira/browse/ACCUMULO-4113";>ACCUMULO-4113</a>
Fixed widespread misuse of ByteBuffer</li>
</ul>
<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
