This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new c26cc39 Automatic Site Publish by Buildbot
c26cc39 is described below
commit c26cc399f14d2c349c7a3ecd658e38669e6960ae
Author: buildbot <[email protected]>
AuthorDate: Wed Aug 26 15:04:47 2020 +0000
Automatic Site Publish by Buildbot
---
output/feed.xml | 501 +++++++++++-------------------
output/index.html | 14 +-
output/news/index.html | 7 -
output/release/accumulo-1.10.0/index.html | 7 +-
output/release/index.html | 15 +-
output/search_data.json | 2 +-
6 files changed, 196 insertions(+), 350 deletions(-)
diff --git a/output/feed.xml b/output/feed.xml
index 449defe..ad8a3ac 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,329 +6,12 @@
</description>
<link>https://accumulo.apache.org/</link>
<atom:link href="https://accumulo.apache.org/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Wed, 26 Aug 2020 14:30:10 +0000</pubDate>
- <lastBuildDate>Wed, 26 Aug 2020 14:30:10 +0000</lastBuildDate>
+ <pubDate>Wed, 26 Aug 2020 15:04:42 +0000</pubDate>
+ <lastBuildDate>Wed, 26 Aug 2020 15:04:42 +0000</lastBuildDate>
<generator>Jekyll v4.1.1</generator>
<item>
- <title>Accumulo 1.10.0 (Draft)</title>
- <description><p>28 August 2020</p>
-
-<p>Apache Accumulo 1.10 is a maintenance release of the 1.9.3 version
with additional internal
-improvements. This release raises the Java language level for the source code
-from 1.7 to 8 and requires a Java runtime environment of Java 8 or later. The
source code level
-change aligns the Accumulo code base Java language version requirements with
the 2.0 branches and
-allows Java language enhancements such as lambda expressions and improved
interface features to be
-used in all active branches of the Accumulo code base.</p>
-
-<p>With the adoption of <a
href="https://semver.org/spec/v2.0.0.html">semver</a>, the
minor number version change
-(from 1.9 to 1.10) signals this release does not modify the Accumulo public
API, but that the
-release contains internal improvements beyond changes that are permitted by
semver in a patch
-release. This release contains contributions from more than 13 contributors
from the Apace Accumulo
-community in over 80 commits and 16 months of work since the 1.9.3 release.
The following release
-notes highlight some of the changes. If anything is missing from this list,
please
-<a
href="https://accumulo.apache.org/contact-us">contact</a>
the developers to have it included.</p>
-
-<h2 id="long-term-support-lts">Long Term Support
(LTS)</h2>
-
-<p>The Apache Accumulo community has adopted a formal Long Term Support
(LTS) release policy. Accumulo
-version 1.10 is the first LTS version and is expected to be the last major /
minor release of the
-1.x line. With the LTS designation, 1.10.0 will receive critical bug and
security fixes for the
-defined support period. No new features will be added to the 1.10 line and
all new feature
-development will occur on the 2.x line.</p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">Version</th>
- <th style="text-align: left">Release Date</th>
- <th style="text-align: left">Maintenance
Period</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align: left">1.10.x</td>
- <td style="text-align: left">31 Aug 2020</td>
- <td style="text-align: left">2 years</td>
- </tr>
- <tr>
- <td style="text-align: left">2.1.x</td>
- <td style="text-align: left">4th Quarter 2020</td>
- <td style="text-align: left">2 years</td>
- </tr>
- </tbody>
-</table>
-
-<p>Users of 1.9.3 or earlier are urged to upgrade to 1.10.0 and to
consider the starting the migration
-to prepare for the Accumulo 2.1.0 release. If you would like to start
preparing for 2.1.0 now, one way to do this is to start building and testing
the next version of your software against Accumulo 2.0.0.</p>
-
-<h2 id="notable-changes">Notable Changes</h2>
-
-<h3 id="bug-fixes">Bug Fixes</h3>
-
-<h4
id="addressed-multiple-possible-concurrency-issues">Addressed
multiple possible concurrency issues</h4>
-<ul>
- <li>Prevent multiple threads from working on same bulk file. (Issue
#1153)</li>
- <li>Avoid multiple threads loading same cache block (Issue
#990)</li>
- <li>Eliminate task creation leak caused by the addition of a new,
additional timed-task for every GC
-run by creating on time-tasked instance in the GC (Issue #1314) (PR
#1318)</li>
- <li>Fix ConcurrentModificationException in HostRegexTableLoadBalancer
(#1107)</li>
-</ul>
-
-<h4
id="improve-metadata-and-root-table-processing-to-prevent-corruption-during-gc">Improve
metadata and root table processing to prevent corruption during GC.</h4>
-<ul>
- <li>Prevent cloning of the metadata table. Cloning the metadata table
could result in losing
-files for either the clone, or the original metadata table during GC
processing (Issue #1309)</li>
- <li>Improve GC handling of WALs used by root tablet. If the root
tablet had WALs, the GC did
-not consider them during collection. (PR #1310)</li>
-</ul>
-
-<h4 id="fix-issue-with-minor-compactions">Fix issue with minor
compactions</h4>
-<p>Added retry to minor compaction thread(s) to prevent transient
iterator issues blocking
-forever (#1644).</p>
-
-<h4
id="strengthened-checks-for-fate-rpc-arguments">Strengthened
checks for FATE RPC arguments</h4>
-<ul>
- <li>Accumulo 2.0 allows extra arguments at table creation. This fix
strengths checks for FATE RPC
-arguments so that unexpected, extra arguments throw an exception instead of
being silently being
-ignored if run against pre 2.0 code (Issue #1141)</li>
-</ul>
-
-<h4 id="address-recovery-performance-issues">Address recovery
performance issues</h4>
-<ul>
- <li>Fix WAL recovery performance issue by adding a temporarily cache
for the existence of recovery
-wals For the case where a lot of tablet servers died, the master was
frequently checking
-for the existence of a recovery log for each tablet. It is very likely that
many tablets point to
-the same recovery logs so the existence checks are redundant. This patch
caches the result of
-existence checks for a short period. (#1462)</li>
- <li>Decrease recovery cache time - reduces NN exists calls
(#1526)</li>
-</ul>
-
-<h4 id="fix-handling-of-client-options">Fix handling of client
options</h4>
-<ul>
- <li>Validate ClientOpts instance name and Zookeeper paths to fix issue
where default client
-configuration was not being used. This change allows either the default
configuration, or the
-command line set the instance name. (#1478)</li>
- <li>Ensures correct use of ZooKeeper getAcl (#1185)</li>
- <li>Expanded InputConfigurator permissions checks to include
Namespace.READ (#1371)</li>
-</ul>
-
-<h4 id="fix-monitor-trace-display">Fix monitor trace
display</h4>
-<ul>
- <li>Fix regression where trace information could not be displayed in
the accumulo monitor.(Issue #1401)</li>
-</ul>
-
-<h3 id="improvements">Improvements</h3>
-
-<h4 id="improve-tablet-logging-for-hot-spot-detection">Improve
tablet logging for hot-spot detection</h4>
-<ul>
- <li>Improve Logging of busy tablets. The deltas of tablets ingest and
query counts are used for
-computing the busiest N tablets. The previous code used the absolute
counts.</li>
- <li>Fixed prioQ that was not properly tracking the top N tablets.(PR
#1291)</li>
- <li>Improve busy tracker handling of reloaded tablets (PR
#1296)</li>
-</ul>
-
-<h4 id="tserver-start-up-and-shutdown-protections">tserver
start-up and shutdown protections:</h4>
-<ul>
- <li>Add option to check for a threshold number of servers to be
registered and available on start-up
-before the master begins tablet assignments when master acquires lock on
start-up. The options
-allow for threshold number of servers and an optional max wait period.<br
/>
-See <a href="#Property Change Summary">Property
Changes</a> for property additions. (#1158)</li>
- <li>Add throttle for the number of shutdown requests sent by the
master to tservers (Issue #1456)</li>
-</ul>
-
-<h4 id="optional-gc-metadata-operations">Optional GC metadata
operations.</h4>
-<ul>
- <li>Added a property - gc.use.full.compaction At the completion of a
GC cycle, the GC compacted the
-metadata table to ensure that GC changes were flushed and persisted. The
property allows for the
-action to be specified as compaction, flush or none. (#1352)</li>
-</ul>
-
-<h4 id="zookeeper-35-version-support">Zookeeper 3.5 version
support</h4>
-<ul>
- <li>Support ZooKeeper 3.4 and 3.5 - Update for ZK 3.5 jar location
changes (#1503)</li>
-</ul>
-
-<h4 id="update-log-statements">Update log
statements:</h4>
-<p>Compacting a table without user iterators was logging like it was an
abnormal condition (#1347)
-Reduce verbose logging of merge operations in Master log (#1338)
-Improve logging for session expired events. When a tserver looses lock, the
Session expired message
-is a log statement for every watcher - reduce current message to trace and add
summary (#1108)</p>
-
-<h4 id="improve-shel-commands-command">Improve shel commands
command</h4>
-<ul>
- <li>Add optional -t tablename to importdirectory shell command.
(#1299)</li>
- <li>Fix idempotency bug in importtable (#1555)</li>
-</ul>
-
-<h4 id="add-gc-hadoop2-metrics">Add GC hadoop2
metrics.</h4>
-<p>Add GC cycle metrics (file and wal collection) to be reported via the
hadoop2 metrics. This exposes
-the gc cycle metrics available in the monitor to external metrics systems and
includes run time
-for the gc post operation (compact, flush). (#1352)</p>
-<ul>
- <li>AccGcStarted - timestamp of GC cycle start</li>
- <li>AccGcFinished - timestamps of GC cycle finished</li>
- <li>AccGcCandidates - Number of candidates for GC</li>
- <li>AccGcInUse - Number of candidates still in use</li>
- <li>AccGcDeleted - Number of candidates deleted</li>
- <li>AccGcErrors - Number of deletion errors</li>
- <li>AccGcWalStarted - timestamp of WAL collection start</li>
- <li>AccGcWalFinished - timestamp of WAL collection
completion</li>
- <li>AccGcWalCandidates - number of WAL candidates for
collection</li>
- <li>AccGcWalInUse - number of WALs in use</li>
- <li>AccGcWalDeleted - number of WALs deleted</li>
- <li>AccGcWalErrors- number of errors during WAL deletion</li>
- <li>AccGcPostOpDuration - duration of compact / flush</li>
- <li>AccGcRunCycleCount - 1-up cycle count</li>
-</ul>
-
-<h4
id="add-option-allow-clone-table-to-keep-the-clone-offline">Add
option allow clone table to keep the clone offline.</h4>
-<ul>
- <li>Option to leave cloned tables offline (#1475)</li>
- <li>Updated the shell clone command with a -o option</li>
-</ul>
-
-<h4
id="improved-metadata-table-consistency-checking-and-testing-during-gc">Improved
metadata table consistency checking and testing during GC</h4>
-
-<ul>
- <li>During GC scans, an error will be thrown if the GC fails
consistency checks (#1379)</li>
- <li>Added a check to ensure the last tablet was seen. This should
cause an error to be thrown if
-the scanner stops returning data for any reason.</li>
-</ul>
-
-<h3 id="java-language-level-changes">Java Language Level
Changes</h3>
-<p>This lists some of the code changes made to update the Java language
level to Java 8. They are
-listed here to aid migration of client code that may have similar issues
migrating to the updated
-language level (#1467).</p>
-<ul>
- <li>Update to maven compiler source and target to Java 1.8</li>
- <li>Add optional dependency to pom for modernizer
annotations</li>
- <li>Add SuppressModernizer annotation to uses of Guava Predicate in
AccumuloConfiguration and its
-subclasses, Optional in VolumeChooser, and Function in GroupBalancer</li>
- <li>Replace Guava Function, Predicate, Preconditions, Optional and
Iterators where able with java.util equivalents</li>
- <li>Replace core.util.Base64 class with java.util equivalent</li>
- <li>Fix warnings introduced by Java 1.8</li>
- <li>Drop method in MockConfiguration causing compiler warning and made
PropertyFilter in
-AccumuloConfiguration extend guava Predicate</li>
- <li>Rename execute methods in MasterClient and ServerClient, like the
2.0 changes to fix the
-overload warnings</li>
- <li>Add colVis file to ContinuousInputFormat. Fixes #1368
(#1369)</li>
- <li>Fix unused var and generics warning</li>
- <li>Limit UnsynchronizedBuffer maximum size to Integer.MAX_VALUE - 8
(#1523)</li>
- <li>Remove need for ANT on classpath (#1532)</li>
- <li>Update spotbugs and maven enforcer plugin versions</li>
- <li>Rename yield method - future restricted identifier</li>
- <li>Fix javadoc html header elements for newer JDKs</li>
-</ul>
-
-<h3 id="other-changes">Other Changes</h3>
-
-<h4 id="build-improvements--changes">Build Improvements /
Changes</h4>
-<ul>
- <li>Switch to GitHub Actions and improve CI workflow (#1671)</li>
- <li>Switch POM project xml attrs from HTTP to HTTPS</li>
- <li>Add patch file for Java 11 generated apidocs</li>
- <li>Update native map makefile to work with Java 11.</li>
- <li>The makefile was modified to check if javac exists - previously it
checked to see if javah exists
-inorder to determine if java is a JDK or JRE. In Java 11, javah no longer
exists - changed to
-look for javac compiler command that exists in Java 8 and 11.</li>
-</ul>
-
-<h4 id="test-improvements">Test Improvements</h4>
-<ul>
- <li>Make ITs override defaultTimeoutSeconds (#1483)</li>
- <li>Increase timeouts on some slow ITs (#1482)</li>
- <li>Stabilize ChaoticBalancerIT (#1491)</li>
- <li>Increase timeout for GarbageCollectWALIT to allow
recovery</li>
- <li>Improve importDirectory tests from #1299</li>
- <li>Limit log size in Travis CI builds</li>
-</ul>
-
-<h1 id="new-properties">New Properties</h1>
-
-<p>Set server count threshold and maximum wait time on start-up before
master begins tablet assignments:</p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">Property</th>
- <th style="text-align: left">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align:
left">master.startup.tserver.avail.min.count</td>
- <td style="text-align: left">the number of required
tservers</td>
- </tr>
- <tr>
- <td style="text-align:
left">master.startup.tserver.avail.max.wait</td>
- <td style="text-align: left">the max time willing to
wait before assigning tablets if threshold count has not been
reached.</td>
- </tr>
- </tbody>
-</table>
-
-<p>Enable improved tserver logging for hot-spot detection:</p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">Property</th>
- <th style="text-align: left">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align:
left">tserver.log.busy.tablets.count</td>
- <td style="text-align: left">the number of busiest
tablets to log. Logged at interval controlled by
tserver.log.busy.tablets.interval. If &lt;= 0, logging of busy tablets is
disabled.</td>
- </tr>
- <tr>
- <td style="text-align:
left">tserver.log.busy.tablets.interval</td>
- <td style="text-align: left">Time interval between
logging out busy tablets information.</td>
- </tr>
- </tbody>
-</table>
-
-<p>GC changes:</p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">Property</th>
- <th style="text-align: left">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align:
left">gc.post.metadata.action</td>
- <td style="text-align: left">Allowed values: compact -
default, current behavior, the metadata table is flushed and compacted on each
GC run. flush - only flush the metadata table, compactions will occur according
to number of files compaction rules. none - take no action.</td>
- </tr>
- <tr>
- <td style="text-align:
left">gc.metrics.enabled</td>
- <td style="text-align: left">Enable detailed gc metrics
reporting with hadoop metrics.</td>
- </tr>
- </tbody>
-</table>
-
-<h1 id="useful-links">Useful links</h1>
-
-<p>(TODO - make actual links)</p>
-
-<p>Release VOTE email thread
-All changes since 1.9.3
-GitHub - List of issues tracked on GitHub corresponding to this release
-1.9.3 release notes - Release notes showing changes in the previous
release</p>
-</description>
- <pubDate>Sat, 29 Feb 2020 00:00:00 +0000</pubDate>
- <link>https://accumulo.apache.org/release/accumulo-1.10.0/</link>
- <guid
isPermaLink="true">https://accumulo.apache.org/release/accumulo-1.10.0/</guid>
-
-
- <category>release</category>
-
- </item>
-
- <item>
<title>Microsoft MASC, an Apache Spark connector for Apache
Accumulo</title>
<description><h1 id="overview">Overview</h1>
<p><a
href="https://github.com/microsoft/masc">MASC</a> provides
an Apache Spark native connector for Apache Accumulo to integrate the rich
Spark machine learning eco-system with the scalable and secure data storage
capabilities of Accumulo.</p>
@@ -1725,5 +1408,185 @@ for using Spark with Accumulo.</p>
</item>
+ <item>
+ <title>Apache Accumulo 1.9.3</title>
+ <description><p>Apache Accumulo 1.9.3 contains bug fixes for
Write Ahead Logs and compaction.
+Users of 1.9.2 are encouraged to upgrade.</p>
+
+<ul>
+ <li><a href="/1.9/accumulo_user_manual.html">User
Manual</a> - In-depth developer and administrator documentation</li>
+ <li><a href="/1.9/apidocs/">Javadocs</a> -
Accumulo 1.9 API</li>
+ <li><a href="/1.9/examples/">Examples</a> - Code
with corresponding readme files that give step by
+step instructions for running example code</li>
+</ul>
+
+<h2 id="notable-changes">Notable Changes</h2>
+
+<h3 id="multiple-fixes-for-write-ahead-logs">Multiple Fixes
for Write Ahead Logs</h3>
+
+<p>This release fixes Write Ahead Logs issues that slow or prevent
recovery
+and in some cases lead to data loss. The fixes reduce the number of WALS
+referenced by a tserver, improve error handing, and improve clean up.</p>
+
+<ul>
+ <li>
+ <p>Eliminates a race condition that could result in data loss during
recovery.
+If the GC deletes unreferenced WALs from ZK while the master is reading
+recovery WALs from ZK, the master may skip WALs it should not, resulting in
+data loss. Fixed in <a
href="https://github.com/apache/accumulo/issues/866">#866</a>.</p>
+ </li>
+ <li>
+ <p>Opening a new WAL in DFS may fail, but still be advertised in ZK.
This could
+result in a missing WAL during recovery, preventing tablets from loading.
+There is no data loss in this case, just WAL references that should not exists.
+Reported in <a
href="https://github.com/apache/accumulo/issues/949">#949</a>
and fixed in <a
href="https://github.com/apache/accumulo/issues/1057">#1005</a>.</p>
+ </li>
+ <li>
+ <p>tserver failures could result in many empty WALs that
unnecessarily slow recovery.
+This was fixed in <a
href="https://github.com/apache/accumulo/issues/845">#823</a>.</p>
+ </li>
+ <li>
+ <p>Some write patterns caused tservers to unnecessarily reference a
lot of WALs,
+which could slow any recovery. In <a
href="https://github.com/apache/accumulo/issues/860">#854</a>
the max WALs referenced was
+limited regardless of the write pattern, avoiding long recovery
times.</p>
+ </li>
+ <li>
+ <p>During tablet recovery, filter out logs that do not define the
tablet. <a
href="https://github.com/apache/accumulo/issues/881">#881</a></p>
+ </li>
+ <li>
+ <p>If a tserver fails sorting, a marker file is written to the
recovery directory.
+This marker prevents any subsequent recovery attempts from succeeding.
+Fixed by modifying the WAL RecoveryLogReader to handle failed file markers in
<a
href="https://github.com/apache/accumulo/issues/1048">#961</a>.</p>
+ </li>
+ <li>
+ <p>Improve performance of serializing mutations to a WAL by avoiding
frequent synchronization. <a
href="https://github.com/apache/accumulo/issues/669">#669</a></p>
+ </li>
+</ul>
+
+<h3 id="multiple-fixes-for-compaction-issues">Multiple Fixes
for Compaction Issues</h3>
+
+<ul>
+ <li>
+ <p>Stop locking during compaction. Compactions acquired the tablet
lock between each
+key value. This created unnecessary contention with other operations like scan
and
+bulk imports. The synchronization was removed <a
href="https://github.com/apache/accumulo/issues/1032">#1031</a>.</p>
+ </li>
+ <li>
+ <p>Only re-queue compaction when there is activity. <a
href="https://github.com/apache/accumulo/issues/759">#759</a></p>
+ </li>
+</ul>
+
+<h3
id="fix-arrayoutofbounds-error-when-new-files-are-created-affects-all-previous-versions">Fix
ArrayOutOfBounds error when new files are created (affects all previous
versions)</h3>
+
+<p>If the 7 digit base 36 number used to name files attempted to go to 8
digits,
+then compactions would fail. This was fixed in <a
href="https://github.com/apache/accumulo/issues/562">#562</a>.</p>
+
+<h3
id="updated-master-metrics-to-include-fate-metrics">Updated Master
Metrics to include FATE metrics.</h3>
+
+<p>Added master metrics to provide a snapshot of current FATE
operations. The metrics added:</p>
+<ul>
+ <li>the number of current FATE transactions in progress,</li>
+ <li>the count of child operations that have occurred on the zookeeper
FATE node</li>
+ <li>a count of zookeeper connection errors when the snapshot is
taken.</li>
+</ul>
+
+<p>The number of child operations provides a light-weight surrogate for
FATE transaction
+progression between snapshots. The metrics are controlled with the following
properties:</p>
+
+<ul>
+ <li>master.fate.metrics.enabled - default to
<em>false</em> preserve current metric reporting</li>
+ <li>master.fate.metrics.min.update.interval - default to
<em>60s</em> - there is a hard limit of 10s.</li>
+</ul>
+
+<p>When enabled, the metrics are published to JMX and can optionally be
configured using standard
+hadoop metrics2 configuration files.</p>
+
+<h3
id="fixed-issues-with-native-maps-with-libstdc-82-and-higher">Fixed
issues with Native Maps with libstdc++ 8.2 and higher</h3>
+
+<p>Versions of libstdc++ 8.2 and higher triggered errors within within
the native map code.
+This release fixes issues <a
href="https://github.com/apache/accumulo/issues/767">#767</a>,
<a
href="https://github.com/apache/accumulo/issues/769">#769</a>,
<a href="https://github.com/apache/accumulo/issues/1064">#1064
</a>, and <a
href="https://github.com/apache/accumulo/issues/1070">#1070
</a>.</p>
+
+<h3 id="fixed-splitting-tablets-with-files-and-no-data">Fixed
splitting tablets with files and no data</h3>
+
+<p>The split code assumed that if a tablet had files that it had data in
+those files. There are some edge case where this is not true. Updated
+the split code to handle this <a
href="https://github.com/apache/accumulo/issues/999">#998</a>.</p>
+
+<h3 id="log-when-a-scan-waits-a-long-time-for-files">Log when
a scan waits a long time for files.</h3>
+
+<p>Accumulo has a configurable limit on the max number of files open in a
+tserver for all scans. When too many files are open, scans must wait.
+In <a
href="https://github.com/apache/accumulo/issues/978">#978</a>
and <a
href="https://github.com/apache/accumulo/issues/981">#981</a>
scans that wait too long for files now log a message.</p>
+
+<h3 id="fixed-race-condition-in-table-existence-check">Fixed
race condition in table existence check.</h3>
+
+<p>The Accumulo client code that checks if tables exists had a race
+condition. The race was fixed in <a
href="https://github.com/apache/accumulo/issues/768">#768</a>
and <a
href="https://github.com/apache/accumulo/issues/973">#973</a></p>
+
+<h3 id="support-running-mini-accumulo-using-java-11">Support
running Mini Accumulo using Java 11</h3>
+
+<p>Mini Accumulo made some assumptions about classloaders that were no
+longer true in Java 11. This caused Mini to fail in Java 11. In
+<a
href="https://github.com/apache/accumulo/issues/924">#924</a>
Mini was updated to work with Java 11, while still working
+with Java 7 and 8.</p>
+
+<h3 id="fixed-issue-with-improperly-configured-snappy">Fixed
issue with improperly configured Snappy</h3>
+
+<p>If snappy was configured and the snappy libraries were not available
then minor
+compactions could hang forever. In <a
href="https://github.com/apache/accumulo/issues/920">#920</a>
and <a
href="https://github.com/apache/accumulo/issues/925">#925</a>
this was fixed and minor
+compactions will proceed when a different compression is configured.</p>
+
+<h3 id="handle-bad-locality-group-config">Handle bad locality
group config.</h3>
+
+<p>Improperly configured locality groups could cause a tablet to become
+inoperative. This was fixed in <a
href="https://github.com/apache/accumulo/issues/819">#819</a>
and <a
href="https://github.com/apache/accumulo/issues/840">#840</a>.</p>
+
+<h3 id="fixed-bulk-import-race-condition">Fixed bulk import
race condition.</h3>
+
+<p>There was a race condition in bulk import that could result in files
+being imported after a bulk import transaction had completed. In the
+worst case these files were already compacted and garbage collected.
+This would cause a tablet to have a reference to a file that did not
+exists. No data would have been lost, but it would cause scans to fail.
+The race was fixed in <a
href="https://github.com/apache/accumulo/issues/800">#800</a>
and <a
href="https://github.com/apache/accumulo/issues/837">#837</a></p>
+
+<h3 id="fixed-issue-with-hostregextableloadbalancer">Fixed
issue with HostRegexTableLoadBalancer</h3>
+
+<p>This addresses an issue when using the HostRegexTableLoadBalancer
+when the default pool is empty. The load balancer will not assign the tablets
at all.
+Here, we select a random pool to assign the tablets to. This behavior is on by
+default in the HostRegexTableLoadBalancer but can be disabled via
+HostRegexTableLoadBalancer configuration setting
+
<em>table.custom.balancer.host.regex.HostTableLoadBalancer.ALL</em>
+ Fixed in <a
href="https://github.com/apache/accumulo/issues/691">#691</a>
- backported to 1.9 in <a
href="https://github.com/apache/accumulo/issues/710">#710</a></p>
+
+<h3 id="update-to-libthrift-version">Update to libthrift
version</h3>
+
+<p>The packaged, binary tarball contains updated version of libthrift
to version 0.9.3-1 to
+address thrift CVE. Issue <a
href="https://github.com/apache/accumulo/issues/1029">#1029</a></p>
+
+<h2 id="useful-links">Useful links</h2>
+
+<ul>
+ <li><a
href="https://lists.apache.org/thread.html/62a490ee3005ef2ec1f3865f6a9539efc082abc49c90892b49005eed@%3Cdev.accumulo.apache.org%3E">Release
VOTE email thread</a></li>
+ <li><a
href="https://github.com/apache/accumulo/compare/rel/1.9.2...apache:rel/1.9.3">All
Changes since 1.9.2</a></li>
+ <li><a
href="https://github.com/apache/accumulo/issues?q=project%3Aapache%2Faccumulo%2F7">GitHub</a>
- List of issues tracked on GitHub corresponding to this release</li>
+ <li><a href="/release/accumulo-1.9.2/">1.9.2 release
notes</a> - Release notes showing changes in the previous
release</li>
+</ul>
+
+<h2 id="upgrading">Upgrading</h2>
+
+<p>View the <a
href="/docs/2.x/administration/upgrading">Upgrading Accumulo
documentation</a> for guidance.</p>
+
+</description>
+ <pubDate>Wed, 10 Apr 2019 00:00:00 +0000</pubDate>
+ <link>https://accumulo.apache.org/release/accumulo-1.9.3/</link>
+ <guid
isPermaLink="true">https://accumulo.apache.org/release/accumulo-1.9.3/</guid>
+
+
+ <category>release</category>
+
+ </item>
+
</channel>
</rss>
diff --git a/output/index.html b/output/index.html
index 4f80dbf..1f2f10e 100644
--- a/output/index.html
+++ b/output/index.html
@@ -180,13 +180,6 @@
<div class="row latest-news-item">
<div class="col-sm-12" style="margin-bottom: 5px">
<span style="font-size: 12px; margin-right: 5px;">Feb 2020</span>
- <a href="/release/accumulo-1.10.0/">Accumulo 1.10.0 (Draft)</a>
- </div>
- </div>
-
- <div class="row latest-news-item">
- <div class="col-sm-12" style="margin-bottom: 5px">
- <span style="font-size: 12px; margin-right: 5px;">Feb 2020</span>
<a href="/blog/2020/02/26/accumulo-spark-connector.html">Microsoft
MASC, an Apache Spark connector for Apache Accumulo</a>
</div>
</div>
@@ -212,6 +205,13 @@
</div>
</div>
+ <div class="row latest-news-item">
+ <div class="col-sm-12" style="margin-bottom: 5px">
+ <span style="font-size: 12px; margin-right: 5px;">Sep 2019</span>
+ <a href="/blog/2019/09/17/erasure-coding.html">Using HDFS Erasure
Coding with Accumulo</a>
+ </div>
+ </div>
+
<div id="news-archive-link">
<p>View all posts in the <a href="/news">news archive</a></p>
</div>
diff --git a/output/news/index.html b/output/news/index.html
index a6e7604..785d167 100644
--- a/output/news/index.html
+++ b/output/news/index.html
@@ -148,13 +148,6 @@
<div class="row" style="margin-top: 15px">
- <div class="col-md-1">Feb 29</div>
- <div class="col-md-10"><a href="/release/accumulo-1.10.0/">Accumulo 1.10.0
(Draft)</a></div>
- </div>
-
-
-
- <div class="row" style="margin-top: 15px">
<div class="col-md-1">Feb 26</div>
<div class="col-md-10"><a
href="/blog/2020/02/26/accumulo-spark-connector.html">Microsoft MASC, an Apache
Spark connector for Apache Accumulo</a></div>
</div>
diff --git a/output/release/accumulo-1.10.0/index.html
b/output/release/accumulo-1.10.0/index.html
index 962ffea..35c666e 100644
--- a/output/release/accumulo-1.10.0/index.html
+++ b/output/release/accumulo-1.10.0/index.html
@@ -140,15 +140,18 @@
<h1 class="title">Accumulo 1.10.0 (Draft)</h1>
- <p>29 Feb 2020</p>
+ <p>26 Aug 2020</p>
+<div class="alert alert-info" style="margin-bottom: 0px;" role="alert">
+ <p>These are <strong>draft</strong> release notes for a future release of
Accumulo!</p>
+ <p>Please view <a class="alert-link" href="/release/accumulo-2.0.0/">the
latest release notes</a>.</p>
+</div>
-<p>28 August 2020</p>
<p>Apache Accumulo 1.10 is a maintenance release of the 1.9.3 version with
additional internal
improvements. This release raises the Java language level for the source code
diff --git a/output/release/index.html b/output/release/index.html
index ddb4886..999c388 100644
--- a/output/release/index.html
+++ b/output/release/index.html
@@ -145,24 +145,11 @@
-<h3>2020</h3>
+<h3>2019</h3>
<div class="row" style="margin-top: 15px">
- <div class="col-md-1">Feb 29</div>
-
- <div class="col-md-10"><strong><a
href="/release/accumulo-1.10.0/">Accumulo 1.10.0
(Draft)</a> ⇐ current</strong></div>
-
- </div>
-
-
-
-
- <hr />
- <h3>2019</h3>
-
- <div class="row" style="margin-top: 15px">
<div class="col-md-1">Aug 02</div>
<div class="col-md-10"><strong><a href="/release/accumulo-2.0.0/">Apache
Accumulo 2.0.0</a> ⇐ current</strong></div>
diff --git a/output/search_data.json b/output/search_data.json
index 52c6c96..afb49fe 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -304,7 +304,7 @@
"release-accumulo-1-10-0": {
"title": "Accumulo 1.10.0 (Draft)",
- "content" : "28 August 2020Apache Accumulo 1.10 is a maintenance
release of the 1.9.3 version with additional internal improvements. This
release raises the Java language level for the source code from 1.7 to 8 and
requires a Java runtime environment of Java 8 or later. The source code level
change aligns the Accumulo code base Java language version requirements with
the 2.0 branches and allows Java language enhancements such as lambda
expressions and improved interface features [...]
+ "content" : "Apache Accumulo 1.10 is a maintenance release of
the 1.9.3 version with additional internal improvements. This release raises
the Java language level for the source code from 1.7 to 8 and requires a Java
runtime environment of Java 8 or later. The source code level change aligns
the Accumulo code base Java language version requirements with the 2.0 branches
and allows Java language enhancements such as lambda expressions and improved
interface features to be used in [...]
"url": " /release/accumulo-1.10.0/",
"categories": "release"
}
