This is an automated email from the ASF dual-hosted git repository.
ddanielr 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 dc80b1a21 Updated 4.x Fate and Replication pages (#499)
dc80b1a21 is described below
commit dc80b1a2171b423cf695931119d519d78354a3e2
Author: Dave Marion <[email protected]>
AuthorDate: Tue Oct 27 11:30:25 2026 -0400
Updated 4.x Fate and Replication pages (#499)
Co-authored-by: Daniel Roberts ddanielr <[email protected]>
---
_docs-4/administration/fate.md | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/_docs-4/administration/fate.md b/_docs-4/administration/fate.md
index 5ad55b0ea..08161f126 100644
--- a/_docs-4/administration/fate.md
+++ b/_docs-4/administration/fate.md
@@ -36,6 +36,11 @@ a REPO is pushed onto a per-transaction REPO stack. The top
of the stack always
next REPO the FATE transaction should execute. When a REPO is successful it
may return another
REPO which is pushed on the stack.
+### FATE Storage
+
+In prior versions all FATE transaction information was stored in ZooKeeper.
Accumulo 4.0 introduces
+a fate table in the system namespace that stores user initiated FATE
transactions.
+
### FATE Structure in ZooKeeper
The storage layer in ZooKeeper is organized by storing each FATE transaction
in a unique path based
@@ -77,10 +82,10 @@ The `fate` admin command accepts a number of arguments for
different functionali
The command for launching the fate admin command is:
```
-> accumulo admin fate --[option]
+> accumulo inst fate --[option]
```
-The Accumulo admin help command option `accumulo admin -h` shows the expected
usage information for the fate and
+The Accumulo help command option `accumulo inst fate -h` shows the expected
usage information for the fate and
other admin commands.
### List/Print
