Skip to content

Updated 4.x design, features, and quickstart user manual pages - #487

Open
dlmarion wants to merge 1 commit into
apache:mainfrom
dlmarion:4_docs_update1
Open

Updated 4.x design, features, and quickstart user manual pages#487
dlmarion wants to merge 1 commit into
apache:mainfrom
dlmarion:4_docs_update1

Conversation

@dlmarion

@dlmarion dlmarion commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@dlmarion dlmarion self-assigned this Sep 8, 2026

@phrocker phrocker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good otherwise. take a look at the comments and use your judgement. I wasn't sure about the design.md changes I made a suggestion, but I don't know if that's a good way of putting it.

In order to manage the number of files per tablet, periodically the TabletServer
performs Major Compactions of files within a tablet, in which some set of RFiles
In order to manage the number of files per tablet, periodically the Manager will
instruct a Compactor to perform a Major Compaction of files within a tablet, in which some set of RFiles

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sort of pull , right? "the Manager identifies the compaction work to be done and a Compactor requests and executes it."


```
accumulo init
accumulo inst init

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not seeing it here, but is there an example for the group keyed maps? I looked at the raw ? I have something like this on my deployments:

tserver:
default:
servers_per_host: 2
hosts:
- host1
- host2

Multiple Coordinators may be run. The Coordinators will choose among themselves a single active Coordinator,
and the others will become backups if the active Coordinator should fail.
Compactors also perform recovery of a tablet
that was previously on a Tablet Server that failed, reapplying any writes

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth saying something like this? The paragraphs below and this are identical, so maybe similar wording for both?
"Compactors also perform the sorting phase of write-ahead log recovery for tablets that were on a Tablet Server that failed. Once sorting completes, the tablet is assigned to a Tablet Server, which replays the sorted mutations."

[sserver]: {% durl configuration/files#sserver %}
[Uno]: https://github.com/apache/fluo-uno
[Uno]: https://github.com/apache/accumulo-uno
[Muchos]: https://github.com/apache/fluo-muchos

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[Muchos]: https://github.com/apache/fluo-muchos
[Muchos]: https://github.com/apache/accumulo-muchos

This repo is deprecated now so not sure if we still want to point to it or not

Multiple managers can be configured. Zookeeper locks are used to determine
which manager is active. The remaining managers simply wait for the current
manager to lose its lock. Current manager state is held in the metadata table
which manager is the primary manager. The remaining managers simply wait for the current

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we say it elsewhere but to me, "remaining managers simply wait" make it sound like they do nothing else besides wait.

### Tracer
The Compaction Coordinator is a function that the primary Manager performs to coordinate
the completion of major compactions using Compactor processes. The Coordinator is responsible
for identifying what external compaction work needs to be done, and the Compactors

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
for identifying what external compaction work needs to be done, and the Compactors
for identifying what external compaction work needs to be done, and for communicating with the Compactors

The Accumulo Compactor process is an application that can be used to run compactions
outside of the TabletServer. One to many Compactors can be run on a cluster and each Compactor
process performs one compaction at a time. The Compactor registers its existence in ZooKeeper
and communicates with the Compaction Coordinator to retrieve its work and to register the

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Searching for "Compaction Coordinator" and "CompactionCoordinator" yields a few more spots that can be cleaned up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants