ddanielr commented on code in PR #454:
URL: https://github.com/apache/accumulo-website/pull/454#discussion_r2035715018
##########
_posts/release/2025-05-01-accumulo-2.1.4.md:
##########
@@ -0,0 +1,144 @@
+---
+title: Apache Accumulo 2.1.4
+sortableversion: '02.01.04'
+draft: true
+LTM: true
+---
+## About
+
+Apache Accumulo 2.1.4 is a patch release of the 2.1 LTM line. It contains bug
+fixes and minor enhancements. This version supersedes 2.1.3. Users upgrading to
+2.1 should upgrade directly to this version instead of 2.1.3.
+
+## Notable Changes
+
+* {% ghi 5446 %} Many dependencies were updated, to include protobuf-java which
+ was updated from 3.22.0 to 3.25.6 due to a vulnerability. Users may run into
+ a runtime exception added in
https://github.com/protocolbuffers/protobuf/pull/20084
+ when using old generated Protobuf files. Users are advised to regenerate
their
+ protobuf files using protobuf 25.6 or later. Alternatively, users can set a
+ system property (see #20084 for details) to suppress the exception.
+
+* {% ghi 5073 %} {% ghi 5034 %} Added `accumulo check-accumulo-properties`
command that can be
+ run before an instance is initialized to check the properties file.
+
+* {% ghi 5193 %} Added `accumulo admin signalShutdown` command to signal the
server
+ process to initiate a graceful shutdown. Compactors will finish the major
compaction
+ that they are currently working on, then will exit. Scan Servers will return
a busy
+ signal to all clients for new scan requests, and will shutdown when all
in-progress
+ scans have closed. Tablet Servers will signal the Manager that they are
shutting down,
+ which should prevent assignment of tablets to that server, then they will
unload all
+ tablets and shut down. The Monitor, Manager, GarbageCollector, and
CompactionCoordinator
+ will shut down also. The last step in the shutdown process for all servers
is to remove
+ their lock in ZooKeeper.
+
+* {% ghi 5438 %} Added `accumulo upgrade --prepare` command which should be
used after
+ shutting down an instance in preparation for an upgrade. This will check
that no Fate
+ transactions exist, delete any ZooKeeper locks for server processes, and
prohibit any
+ server processes from being started.
+
+* {% ghi 4898 %} New way to compute bulk load plans (TODO: Needs text)
+
+* {% ghi 5169 %} {% ghi 5170 %} The TabletServer will halt itself when a walog
write or
+ minc failure occurs and the TabletServer lock is not held in ZooKeeper.
+
+* {% ghi 5145 %} {% ghi 5132 %} The Manager and TabletServer processes now
have a background
+ thread that can be enabled via the property
`general.server.lock.verification.interval` to
+ validate that the process is holding the lock in ZooKeeper. The existing
mechanism of relying
+ on a Watcher to notify the process that the lock has been lost can be a
problem due to the
+ fact that there is a single thread in the ZooKeeper client that fires
Watcher events. If the
+ thread is currently waiting on a hung Watcher, then subsequent Watcher
events will not fire
+ and could leave the server running without a lock.
+
+* {% ghi 5174 %} Improvements to the `accumulo-cluster` and `accumulo-service`
scripts have been
+ backported from the main branch. This includes syntax changes.
+
+* {% ghi 5384 %} {% ghi 5386 %} Fixed an issue with multiple threads
performing AES decryption leading to corrupt data.
+
+### Configurable Improvements
+
+Many notable improvements have been added that include a means for users to
configure them via new
+or existing properties to improve system performance or behavior. These
include:
+
+* {% ghi 4723 %} {% ghi 5239 %} Changes to properties
`tserver.session.idle.max` and
+ `tserver.session.update.idle.max` no longer require a TabletServer restart.
+
+* {% ghi 5078 %} {% ghi 5081} Added property `monitor.extents.obfuscate`
(default true) which can be
Review Comment:
This was reverted: see https://github.com/apache/accumulo/pull/5081
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
