You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "dlmarion (via GitHub)" <gi...@apache.org> on 2026/09/08 16:16:49 UTC

[PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

dlmarion opened a new pull request, #487:
URL: https://github.com/apache/accumulo-website/pull/487

   (no comment)


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3992009330


##########
_docs-4/getting-started/quickstart.md:
##########
@@ -290,10 +288,9 @@ When finished, use the following commands to stop Accumulo:
 [manager]: {% durl configuration/files#managers %}
 [tserver]: {% durl configuration/files#tservers %}
 [tracer]: {% durl configuration/files#tracers %}
-[compaction.coordinator]: {% durl configuration/files#compaction%20coordinator %}
-[compaction.compactor]: {% durl configuration/files#compaction%20compactor %}
+[compactor]: {% durl configuration/files#compaction%20compactor %}
 [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

Review Comment:
   Updated in d4f7fcc



##########
_docs-4/getting-started/features.md:
##########
@@ -64,8 +64,8 @@ can share a pool of datanodes.
 ### Manager fail over
 
 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

Review Comment:
   Updated in d4f7fcc



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3991920108


##########
_docs-4/getting-started/quickstart.md:
##########
@@ -138,7 +138,7 @@ instance.
 The following command will perform the initialization.
 
 ```
-accumulo init
+accumulo inst init

Review Comment:
   You are referring to the cluster.yaml file syntax? The file is mentioned at https://accumulo.apache.org/docs/4.x/configuration/files#clusteryaml, which is not part of this change. It's probably worth documenting the structure just to point out that `default` in your example is the name of a resource group. I wonder if comments in the generated file would be more useful (some people don't read the docs).



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "phrocker (via GitHub)" <gi...@apache.org>.
phrocker commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3978565658


##########
_docs-4/getting-started/design.md:
##########
@@ -171,8 +167,8 @@ locality group. The diagram below shows the logical view and HDFS file view of a
 
 ## Compactions
 
-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

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



##########
_docs-4/getting-started/design.md:
##########
@@ -88,27 +88,19 @@ Multiple Monitors can be run to provide hot-standby support in the face of failu
 forwarding of logs from remote hosts to the Monitor, only one Monitor process should be active
 at one time. Leader election will be performed internally to choose the active Monitor.
 
-### Compactor (experimental)
+### Compactor
 
-The Accumulo Compactor process is an optional application that can be used to run compactions
+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
-completion status of the compaction. The Compactor process will continue to perform compactions
-in situations where normal in-TabletServer compactions would fail, such as TabletServer restart
-and Tablet re-hosting.
-
-### Compaction Coordinator (experimental)
-
-The Accumulo Compaction Coordinator is an optional application that is required to run compactions
-outside of the TabletServer. The Coordinator is responsible for communicating with the
-TabletServers, to identify what external compaction work needs to be done, and the Compactors
-to assign work, get status updates, and cancel running external compactions.
+and communicates with the CompactionCoordinator in the primary Manager to retrieve its work and to register the
+completion status of the compaction.
 
-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

Review Comment:
   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."



##########
_docs-4/getting-started/quickstart.md:
##########
@@ -138,7 +138,7 @@ instance.
 The following command will perform the initialization.
 
 ```
-accumulo init
+accumulo inst init

Review Comment:
   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



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3992010817


##########
_docs-4/getting-started/design.md:
##########
@@ -57,22 +56,23 @@ They will perform leader election among themselves to choose a single active ins
 
 ### Manager
 
-The Accumulo Manager is responsible for detecting and responding to TabletServer
-failure. It tries to balance the load across TabletServer by assigning tablets carefully
+The Accumulo Manager is responsible for managing Tablet, FaTE transaction, and external
+compaction state across the cluster. It assigns and balances the Tablets across TabletServers
 and instructing TabletServers to unload tablets when necessary. The Manager ensures all
 tablets are assigned to one TabletServer each, and handles table creation, alteration,
 and deletion requests from clients. The Manager also coordinates startup, graceful
 shutdown and recovery of changes in write-ahead logs when Tablet servers fail.
 
-Multiple managers may be run. The managers will choose among themselves a single manager,
-and the others will become backups if the manager should fail.
-
-### 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

Review Comment:
   Updated in d4f7fcc



##########
_docs-4/getting-started/design.md:
##########
@@ -88,27 +88,19 @@ Multiple Monitors can be run to provide hot-standby support in the face of failu
 forwarding of logs from remote hosts to the Monitor, only one Monitor process should be active
 at one time. Leader election will be performed internally to choose the active Monitor.
 
-### Compactor (experimental)
+### Compactor
 
-The Accumulo Compactor process is an optional application that can be used to run compactions
+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

Review Comment:
   Updated in d4f7fcc



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion merged PR #487:
URL: https://github.com/apache/accumulo-website/pull/487


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "DomGarguilo (via GitHub)" <gi...@apache.org>.
DomGarguilo commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3982565050


##########
_docs-4/getting-started/quickstart.md:
##########
@@ -290,10 +288,9 @@ When finished, use the following commands to stop Accumulo:
 [manager]: {% durl configuration/files#managers %}
 [tserver]: {% durl configuration/files#tservers %}
 [tracer]: {% durl configuration/files#tracers %}
-[compaction.coordinator]: {% durl configuration/files#compaction%20coordinator %}
-[compaction.compactor]: {% durl configuration/files#compaction%20compactor %}
+[compactor]: {% durl configuration/files#compaction%20compactor %}
 [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

Review Comment:
   ```suggestion
   [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



##########
_docs-4/getting-started/features.md:
##########
@@ -64,8 +64,8 @@ can share a pool of datanodes.
 ### Manager fail over
 
 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

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



##########
_docs-4/getting-started/design.md:
##########
@@ -57,22 +56,23 @@ They will perform leader election among themselves to choose a single active ins
 
 ### Manager
 
-The Accumulo Manager is responsible for detecting and responding to TabletServer
-failure. It tries to balance the load across TabletServer by assigning tablets carefully
+The Accumulo Manager is responsible for managing Tablet, FaTE transaction, and external
+compaction state across the cluster. It assigns and balances the Tablets across TabletServers
 and instructing TabletServers to unload tablets when necessary. The Manager ensures all
 tablets are assigned to one TabletServer each, and handles table creation, alteration,
 and deletion requests from clients. The Manager also coordinates startup, graceful
 shutdown and recovery of changes in write-ahead logs when Tablet servers fail.
 
-Multiple managers may be run. The managers will choose among themselves a single manager,
-and the others will become backups if the manager should fail.
-
-### 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

Review Comment:
   ```suggestion
   for identifying what external compaction work needs to be done, and for communicating with the Compactors
   ```



##########
_docs-4/getting-started/design.md:
##########
@@ -88,27 +88,19 @@ Multiple Monitors can be run to provide hot-standby support in the face of failu
 forwarding of logs from remote hosts to the Monitor, only one Monitor process should be active
 at one time. Leader election will be performed internally to choose the active Monitor.
 
-### Compactor (experimental)
+### Compactor
 
-The Accumulo Compactor process is an optional application that can be used to run compactions
+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

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



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Updated 4.x design, features, and quickstart user manual pages [accumulo-website]

Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on code in PR #487:
URL: https://github.com/apache/accumulo-website/pull/487#discussion_r3992006705


##########
_docs-4/getting-started/design.md:
##########
@@ -171,8 +167,8 @@ locality group. The diagram below shows the logical view and HDFS file view of a
 
 ## Compactions
 
-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

Review Comment:
   Updated in d4f7fcc



##########
_docs-4/getting-started/design.md:
##########
@@ -88,27 +88,19 @@ Multiple Monitors can be run to provide hot-standby support in the face of failu
 forwarding of logs from remote hosts to the Monitor, only one Monitor process should be active
 at one time. Leader election will be performed internally to choose the active Monitor.
 
-### Compactor (experimental)
+### Compactor
 
-The Accumulo Compactor process is an optional application that can be used to run compactions
+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
-completion status of the compaction. The Compactor process will continue to perform compactions
-in situations where normal in-TabletServer compactions would fail, such as TabletServer restart
-and Tablet re-hosting.
-
-### Compaction Coordinator (experimental)
-
-The Accumulo Compaction Coordinator is an optional application that is required to run compactions
-outside of the TabletServer. The Coordinator is responsible for communicating with the
-TabletServers, to identify what external compaction work needs to be done, and the Compactors
-to assign work, get status updates, and cancel running external compactions.
+and communicates with the CompactionCoordinator in the primary Manager to retrieve its work and to register the
+completion status of the compaction.
 
-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

Review Comment:
   Updated in d4f7fcc



-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org