You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2022/04/28 16:52:09 UTC

[GitHub] [druid] vtlim commented on a diff in pull request #12416: Update automatic compaction docs with consistent terminology

vtlim commented on code in PR #12416:
URL: https://github.com/apache/druid/pull/12416#discussion_r861114739


##########
docs/design/coordinator.md:
##########
@@ -79,26 +79,27 @@ If a Historical process restarts or becomes unavailable for any reason, the Drui
 
 To ensure an even distribution of segments across Historical processes in the cluster, the Coordinator process will find the total size of all segments being served by every Historical process each time the Coordinator runs. For every Historical process tier in the cluster, the Coordinator process will determine the Historical process with the highest utilization and the Historical process with the lowest utilization. The percent difference in utilization between the two processes is computed, and if the result exceeds a certain threshold, a number of segments will be moved from the highest utilized process to the lowest utilized process. There is a configurable limit on the number of segments that can be moved from one process to another each time the Coordinator runs. Segments to be moved are selected at random and only moved if the resulting utilization calculation indicates the percentage difference between the highest and lowest servers has decreased.
 
-### Compacting Segments
+### Compacting segments
 
-Each run, the Druid Coordinator compacts segments by merging small segments or splitting a large one. This is useful when your segments are not optimized
-in terms of segment size which may degrade query performance. See [Segment Size Optimization](../operations/segment-optimization.md) for details.
+The Druid Coordinator manages the automatic compaction system.
+Each run, the Coordinator compacts segments by merging small segments or splitting a large one. This is useful when your segments are not optimized
+in terms of segment size which may degrade query performance. See [Segment size optimization](../operations/segment-optimization.md) for details.

Review Comment:
   ```suggestion
   See [Segment size optimization](../operations/segment-optimization.md) for details.
   ```



-- 
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: commits-unsubscribe@druid.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org