accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ctubb...@apache.org
Subject [accumulo-website] branch master updated: Update gems and add 1.9.2 and 1.9.3 draft notes
Date Wed, 18 Jul 2018 21:30:40 GMT
This is an automated email from the ASF dual-hosted git repository.

ctubbsii pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 9a99127  Update gems and add 1.9.2 and 1.9.3 draft notes
9a99127 is described below

commit 9a99127a17085e061479feceace6cef4e813a6a7
Author: Christopher Tubbs <ctubbsii@apache.org>
AuthorDate: Wed Jul 18 17:28:41 2018 -0400

    Update gems and add 1.9.2 and 1.9.3 draft notes
---
 Gemfile.lock                                | 14 ++---
 _posts/release/2018-07-18-accumulo-1.9.2.md | 92 +++++++++++++++++++++++++++++
 _posts/release/2018-07-18-accumulo-1.9.3.md | 72 ++++++++++++++++++++++
 3 files changed, 171 insertions(+), 7 deletions(-)

diff --git a/Gemfile.lock b/Gemfile.lock
index fa1cebe..f0241c7 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -8,8 +8,8 @@ GEM
     em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0.6.0)
-    eventmachine (1.2.5)
-    ffi (1.9.23)
+    eventmachine (1.2.7)
+    ffi (1.9.25)
     forwardable-extended (2.6.0)
     http_parser.rb (0.6.0)
     i18n (0.9.5)
@@ -33,8 +33,8 @@ GEM
       sass (~> 3.4)
     jekyll-watch (2.0.0)
       listen (~> 3.0)
-    kramdown (1.16.2)
-    libv8 (3.16.14.19-x86_64-linux)
+    kramdown (1.17.0)
+    libv8 (3.16.14.19)
     liquid (4.0.0)
     listen (3.1.5)
       rb-fsevent (~> 0.9, >= 0.9.4)
@@ -43,15 +43,15 @@ GEM
     mercenary (0.3.6)
     pathutil (0.16.1)
       forwardable-extended (~> 2.6)
-    public_suffix (2.0.5)
+    public_suffix (3.0.2)
     rb-fsevent (0.10.3)
     rb-inotify (0.9.10)
       ffi (>= 0.5.0, < 2)
     ref (2.0.0)
-    rouge (2.2.1)
+    rouge (3.1.1)
     ruby_dep (1.5.0)
     safe_yaml (1.0.4)
-    sass (3.5.6)
+    sass (3.5.7)
       sass-listen (~> 4.0.0)
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
diff --git a/_posts/release/2018-07-18-accumulo-1.9.2.md b/_posts/release/2018-07-18-accumulo-1.9.2.md
new file mode 100644
index 0000000..cfd28ca
--- /dev/null
+++ b/_posts/release/2018-07-18-accumulo-1.9.2.md
@@ -0,0 +1,92 @@
+---
+title: Apache Accumulo 1.9.2
+draft: true
+---
+
+Apache Accumulo 1.9.2 contains fixes for critical write-ahead log bugs.
+Users of any previous version of 1.8 or 1.9 are encouraged to upgrade
+immediately to avoid those issues.
+
+* [User Manual][user_manual] - In-depth developer and administrator documentation
+* [Javadocs][javadoc] - Accumulo 1.9 API
+* [Examples][examples] - Code with corresponding readme files that give step by
+  step instructions for running example code
+
+## Notable Changes
+
+### Fixes for Critical WAL Bugs (affects versions 1.8.0-1.9.1)
+
+Multiple bugs were fixed in 1.9.2 which affects the behavior of the write-ahead
+log mechanism. These vary in significance, ranging from moderate to critical.
+
+* [#537] - (Critical) Since 1.8.0, a bug existed which could cause some
+  write-ahead logs to be removed (garbage collected) before Accumulo was
+  finished with them. These removed logs could have contained important state
+  tracking information.  Without the state contained in these logs, some data
+  in the remaining logs could have been replayed into a table when not needed.
+  This could have reintroduced deleted data, or introduced duplicate data
+  (which can interfere with combiners).
+* [#538] - (Moderate) A bug was introduced in 1.9.1 which resulted in some
+  false positive IllegalStateExceptions to occur, preventing log recovery.
+* [#539] - (Moderate) Since 1.8.0, a race condition existed which could cause a log
+  file which contains data to be recovered to not be recorded, thus making it
+  invisible to recovery, if a tserver died within a very small window. [#441]
+  attempted to fix this in 1.9.1, but the proper fix was done in 1.9.2 with PR
+  [#559].
+
+Even if you primarily use bulk ingest, Accumulo's own metadata tables can be
+affected by these bugs, causing unexpected behavior after an otherwise routine
+and recoverable server failure. As such, these bugs should be a concern to all
+users.
+
+### Fixes for concurrency bugs gathering table information (affects 1.8.0-1.9.1)
+
+Bugs were found with the `master.status.threadpool.size` property. If this
+property were set to a value other than `1`, it could cause 100% CPU, hanging,
+or `ConcurrentModificationException`s.
+
+These bugs were fixed in [#546].
+
+### Monitor time unit bug
+
+A bug was found in the monitor which displayed time durations (for example,
+those pertaining to bulk imports) in incorrect time units.
+
+This bug was fixed in [#553].
+
+## Other Changes
+
+* [GitHub] - List of issues tracked on GitHub corresponding to this release
+* [1.9.1 release notes][prev_notes] - Release notes showing changes in the previous release
+
+## Upgrading
+
+View the [Upgrading Accumulo documentation][upgrade] for guidance.
+
+## Testing
+
+* All ITs passed with Hadoop 3.0.0 (hadoop.profile=3)
+* All ITs passed with Hadoop 2.6.4 (hadoop.profile=2)
+* Ran 3 continuous ingesters successfully for 24 hours on a 10 node cluster
+  with agitation and pausing. Verification for all 3 tests was successful.
+* Ran continuous ingest for 24 hours and verified without agitation on a 10
+  node cluster.
+* Tested [Apache Fluo][fluo] build and ITs passed against this version.
+* Ran a single-node cluster with [Uno] and created a table, ingested data,
+  flushed, compacted, scanned, and deleted the table.
+
+[#441]: https://github.com/apache/accumulo/issues/441
+[#537]: https://github.com/apache/accumulo/issues/537
+[#538]: https://github.com/apache/accumulo/issues/538
+[#539]: https://github.com/apache/accumulo/issues/539
+[#546]: https://github.com/apache/accumulo/issues/546
+[#553]: https://github.com/apache/accumulo/issues/553
+[#559]: https://github.com/apache/accumulo/issues/559
+[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.2
+[Uno]: https://github.com/apache/fluo-uno
+[examples]: {{ site.baseurl }}/1.9/examples/
+[fluo]: https://fluo.apache.org
+[javadoc]: {{ site.baseurl }}/1.9/apidocs/
+[prev_notes]: {{ site.baseurl }}/release/accumulo-1.9.1/
+[upgrade]: {{ site.baseurl }}/docs/2.0/administration/upgrading
+[user_manual]: {{ site.baseurl }}/1.9/accumulo_user_manual.html
diff --git a/_posts/release/2018-07-18-accumulo-1.9.3.md b/_posts/release/2018-07-18-accumulo-1.9.3.md
new file mode 100644
index 0000000..f8da85d
--- /dev/null
+++ b/_posts/release/2018-07-18-accumulo-1.9.3.md
@@ -0,0 +1,72 @@
+---
+title: Apache Accumulo 1.9.3
+draft: true
+---
+
+Apache Accumulo 1.9.3 contains bug fixes for ~summary of bugs here~.
+Users of any previous version of 1.8 or 1.9 are encouraged to upgrade
+~immediately or specify recommended timeline~.
+
+* [User Manual][user_manual] - In-depth developer and administrator documentation
+* [Javadocs][javadoc] - Accumulo 1.9 API
+* [Examples][examples] - Code with corresponding readme files that give step by
+  step instructions for running example code
+
+## Notable Changes
+
+### Fix ArrayOutOfBounds error when new files are created (affects all previous versions)
+
+Accumulo maintains a 1-up counter to keep file names and other identifiers
+unique. This counter is padded with 0 characters when used in file names. If
+the counter becomes sufficiently large, the padding code in versions prior to
+1.9.3 causes an out of bounds error.
+
+Most users will not be affected by this bug, since it requires the counter to
+be very large before the error would be seen. Situations which might cause the
+counter to get very large include: having a very old Accumulo cluster that has
+been running for many years, having a very large cluster, having a cluster that
+writes many files very quickly for long periods of time, having altered the
+current value of the counter in ZooKeeper, or if you experience a bug which
+causes the counter value to skip ahead very rapidly.
+
+If you wish to check to see if you are at risk of being impacted by this bug,
+examine the name of RFiles recently created in your system. If you have one or
+more padded 0 characters (after an initial letter), as in I000zy98.rf or
+I0123abc.rf, you are probably at low risk from this bug.
+
+This issue was fixed in pull request [#562]
+
+### ~Another notable item here~ (affects ~versions~)
+
+More description here. This was fixed in [#NUM].
+
+## Other Changes
+
+* [GitHub] - List of issues tracked on GitHub corresponding to this release
+* [1.9.2 release notes][prev_notes] - Release notes showing changes in the previous release
+
+## Upgrading
+
+View the [Upgrading Accumulo documentation][upgrade] for guidance.
+
+## Testing
+
+* (Example) All ITs passed with Hadoop 3.0.0 (hadoop.profile=3)
+* (Example) All ITs passed with Hadoop 2.6.4 (hadoop.profile=2)
+* (Example) Ran 3 continuous ingesters successfully for 24 hours on a 10 node cluster
+  with agitation and pausing. Verification for all 3 tests was successful.
+* (Example) Ran continuous ingest for 24 hours and verified without agitation on a 10
+  node cluster.
+* (Example) Tested [Apache Fluo][fluo] build and ITs passed against this version.
+* (Example) Ran a single-node cluster with [Uno] and created a table, ingested data,
+  flushed, compacted, scanned, and deleted the table.
+
+[#562]: https://github.com/apache/accumulo/issues/562
+[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.3
+[Uno]: https://github.com/apache/fluo-uno
+[examples]: {{ site.baseurl }}/1.9/examples/
+[fluo]: https://fluo.apache.org
+[javadoc]: {{ site.baseurl }}/1.9/apidocs/
+[prev_notes]: {{ site.baseurl }}/release/accumulo-1.9.2/
+[upgrade]: {{ site.baseurl }}/docs/2.0/administration/upgrading
+[user_manual]: {{ site.baseurl }}/1.9/accumulo_user_manual.html


Mime
View raw message