ArvinZheng commented on a change in pull request #10287:
URL: https://github.com/apache/druid/pull/10287#discussion_r493061492



##########
File path: docs/configuration/index.md
##########
@@ -689,6 +689,7 @@ These Coordinator static configurations can be defined in 
the `coordinator/runti
 |`druid.coordinator.loadqueuepeon.repeatDelay`|The start and repeat delay for 
the loadqueuepeon, which manages the load and drop of segments.|PT0.050S (50 
ms)|
 |`druid.coordinator.asOverlord.enabled`|Boolean value for whether this 
Coordinator process should act like an Overlord as well. This configuration 
allows users to simplify a druid cluster by not having to deploy any standalone 
Overlord processes. If set to true, then Overlord console is available at 
`http://coordinator-host:port/console.html` and be sure to set 
`druid.coordinator.asOverlord.overlordService` also. See next.|false|
 |`druid.coordinator.asOverlord.overlordService`| Required, if 
`druid.coordinator.asOverlord.enabled` is `true`. This must be same value as 
`druid.service` on standalone Overlord processes and 
`druid.selectors.indexing.serviceName` on Middle Managers.|NULL|
+|`druid.coordinator.duties.logUsedSegments.enabled`|Boolean value for whether 
or not the coordinator should execute the `LogUsedSegments` Duty|true|

Review comment:
       +1 to describe more about the behavior of LogUsedSegments duty. Also I 
prefer to remove the `duties` from the config item name -  
`druid.coordinator.logUsedSegments.enabled`. `duties` is a term in the code not 
in the user facing documentation, and before it was called `helpers` in the 
code.




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to