This is an automated email from the ASF dual-hosted git repository.
dlmarion pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/main by this push:
new efce13d5 Begin 2.1.1 release notes (#368)
efce13d5 is described below
commit efce13d50423e7b4c976d256f1728cad1e40ee30
Author: Dave Marion <dlmar...@apache.org>
AuthorDate: Fri Nov 18 10:37:30 2022 -0500
Begin 2.1.1 release notes (#368)
Co-authored-by: Christopher Tubbs <ctubb...@apache.org>
---
_posts/release/2022-11-02-accumulo-2.1.1.md | 54 +++++++++++++++++++++++++++++
1 file changed, 54 insertions(+)
diff --git a/_posts/release/2022-11-02-accumulo-2.1.1.md
b/_posts/release/2022-11-02-accumulo-2.1.1.md
new file mode 100644
index 00000000..2172ef0f
--- /dev/null
+++ b/_posts/release/2022-11-02-accumulo-2.1.1.md
@@ -0,0 +1,54 @@
+---
+title: Apache Accumulo 2.1.1
+sortableversion: '02.01.01'
+LTM: true
+draft: true
+---
+## About
+
+Apache Accumulo 2.1.1 is a patch release of the 2.1.0 LTM line.
+
+### Major Improvements
+
+### Minor Improvements
+
+* {% ghi 3077 %}, {% ghi 3079 %} Avoid filling OS file caches by setting the
+ `FSDataOutputStream.setDropBehind` flag when performing likely one-time file
+ accesses, as with WAL files and major compaction input files. This should
allow
+ files that might benefit more from caching to stay in the cache longer.
+* {% ghi 3023 %}, {% ghi 3053 %} Prevent excessive logging when an
ExternalCompaction
+ is cancelled for cause and around the ThreadPools
+* {% ghi 3057 %} Modified Monitor to direct DataTable errors to console
+
+### Behavior Changes
+
+* {% ghi 3082 %} ScanServers can now scan offline tables. The AccumuloClient
will no longer
+ throw a TableOfflineException when creating a Scanner or BatchScanner
against an offline table.
+ Instead, an error will be thrown on the call to iterator() if it can't be
scanned because it is offline.
+
+### Bug Fixes
+
+* {% ghi 3059 %} Removed stale compactions from CompactionCoordinator internal
structure. The
+ CompactionCoordinator has an internal data structure where it keeps track of
running compactions. Running
+ compactions were not being removed from this set in some edge cases so they
continued to be shown on the
+ Monitor when in reality the compaction was not running. This occured in
testing when the Compactor process
+ was killed by the agitator. The compaction was rescheduled to run on a
different Compactor, the issue here
+ was just orphaned information in the data structure being shown in the
Monitor.
+* {% ghi 3048 %} Output time strings on the monitor using the correct user
locale (also made them more concise)
+
+## Upgrading
+
+View the [Upgrading Accumulo documentation][upgrade] for guidance.
+
+## 2.1.1 GitHub Project
+
+[All tickets related to 2.1.1.][project]
+
+## Known Issues
+
+At the time of release, the following issues were known:
+
+
+[LTM]: {{ site.baseurl }}/contributor/versioning#LTM
+[upgrade]: /docs/2.x/administration/upgrading
+[project]: https://github.com/apache/accumulo/projects/25
