Project: Druid (App Definition and Development / Database)
File: coordinator.md

id: coordinator title: "Coordinator service" sidebar_label: "Coordinator" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> The Coordinator service is primarily responsible for segment management and distribution. More specifically, the Coordinator service communicates to Historical services to load or drop segments based on configurations. The Coordinator is responsible for loading new segments, dropping outdated segments, ensuring that segments are "replicated" (that is, loaded on multiple different Historical nodes) proper (configured) number of times, and moving ("balancing") segments between Historical nodes to keep the latter evenly loaded. The Coordinator runs its duties periodically and the time between each run is a configurable parameter. On each run, the Coordinator assesses the current state of the cluster before deciding on the appropriate actions to take. Similar to the Broker and Historical services, the Coordinator maintains a connection to a ZooKeeper cluster for current cluster information. The Coordinator also maintains a connection to a database containing information about "used" segments (that is, the segments that should be loaded in the cluster) and the loading rules. Before any unassigned segments are serviced by Historical services, the Historical services for each tier are first sorted in terms of capacity, with least capacity servers having the highest priority. Unassigned segments are always assigned to the services with least capacity to maintain a level of balance between services. The Coordinator does not directly communicate with a Historical service when assigning it a new segment; instead the Coordinator creates some temporary information about the new segment under load queue path of the Historical service. Once this request is seen, the Historical service loads the segment and begins servicing it. For Apache Druid Coordinator service configuration, see . For basic tuning guidance for the Coordinator service, see . For a list of API endpoints supported by the Coordinator, see . ``` org.apache.druid.cli.Main server coordinator ``` Segments can be automatically loaded and dropped from the cluster based on a set of rules. For more information on rules, see . On each run, the Coordinator compares the set of used segments in the database with the segments served by some Historical nodes in the cluster. The Coordinator sends requests to Historical nodes to unload unused segments or segments that are removed from the database. Segments that are overshadowed (their versions are too old and their data has been replaced by newer segments) are marked as unused. During the next Coordinator's run, they will be unloaded from Historical nodes in the

On each run, the Coordinator determines and cleans up unneeded eternity tombstone segments for each datasource. These segments must fit all the following criteria: It is a tombstone segment that starts at -INF or ends at INF (for example, a tombstone with an interval of `-146136543-09-08T08:23:32.096Z/2000-01-01` or `2020-01-01/146140482-04-24T15:36:27.903Z` or `-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z`) It does not overlap with any overshadowed segment It has 0 core partitions If a Historical service restarts or becomes unavailable for any reason, the Coordinator will notice a service has gone missing and treat all segments served by that service as being dropped. Given a sufficient period of time, the segments may be reassigned to other Historical services in the cluster. However, each segment that is dropped is not immediately forgotten. Instead, there is a transitional data structure that stores all dropped segments with an associated lifetime. The lifetime represents a period of time in which the Coordinator will not reassign a dropped segment. Hence, if a Historical service becomes unavailable and available again within a short period of time, the Historical service will start up and serve segments from its cache without any those segments being reassigned across the cluster. To ensure an even distribution of segments across Historical services in the cluster, the Coordinator service will find the total size of all segments being served by every Historical service each time the Coordinator runs. For every Historical service tier in the cluster, the Coordinator service will determine the Historical service with the highest utilization and the Historical service with the lowest utilization. The percent difference in utilization between the two services is computed, and if the result exceeds a certain threshold, a number of segments will be moved from the highest utilized service to the lowest utilized service. There is a configurable limit on the number of segments that can be moved from one service 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. The Coordinator manages the . Each run, the Coordinator compacts segments by merging small segments or splitting a large one. This is useful when the size of your segments is not optimized which may degrade query performance. See for details. The Coordinator first finds the segments to compact based on the . Once some segments are found, it issues a to compact those segments. The maximum number of running compaction tasks is `min(sum of worker capacity * slotRatio, maxSlots)`. Note that even if `min(sum of worker capacity * slotRatio, maxSlots) = 0`, at least one compaction task is always submitted if the compaction is enabled for a dataSource. See and to enable and configure automatic compaction. Compaction tasks might fail due to the following reasons: If the input segments of a compaction task are removed or overshadowed before it starts, that compaction task fails immediately. If a task of a higher priority acquires a for an interval overlapping with the interval of a compaction task, the compaction task fails. Once a compaction task fails, the Coordinator simply checks the segments in the interval of the failed task again, and issues another compaction task in the next

Note that Compacting Segments Coordinator Duty is automatically enabled and run as part of the Indexing Service Duties group. However, Compacting Segments Coordinator Duty can be configured to run in isolation as a separate Coordinator duty group. This allows changing the period of Compacting Segments Coordinator Duty without impacting the period of other Indexing Service Duties. This can be done by setting the following properties. For more details, see . ``` druid.coordinator.dutyGroups=[<SOMEGROUPNAME>] druid.coordinator.<SOMEGROUPNAME>.duties=["compactSegments"] druid.coordinator.<SOMEGROUPNAME>.period=<PERIODTORUNCOMPACTINGSEGMENTS_DUTY> ``` At every Coordinator run, this policy looks up time chunks from newest to oldest and checks whether the segments in those time chunks need compaction. A set of segments needs compaction if all conditions below are satisfied: Total size of segments in the time chunk is smaller than or equal to the configured `inputSegmentSizeBytes`. Segments have never been compacted yet or compaction spec has been updated since the last compaction: `maxTotalRows` or `indexSpec`. Here are some details with an example. Suppose we have two dataSources (`foo`, `bar`) as seen below: `foo` `foo2017-11-01T00:00:00.000Z2017-12-01T00:00:00.000Z_VERSION` `foo2017-11-01T00:00:00.000Z2017-12-01T00:00:00.000ZVERSION1` `foo2017-09-01T00:00:00.000Z2017-10-01T00:00:00.000Z_VERSION` `bar` `bar2017-10-01T00:00:00.000Z2017-11-01T00:00:00.000Z_VERSION` `bar2017-10-01T00:00:00.000Z2017-11-01T00:00:00.000ZVERSION1` Assuming that each segment is 10 MB and haven't been compacted yet, this policy first returns two segments of `foo2017-11-01T00:00:00.000Z2017-12-01T00:00:00.000ZVERSION` and `foo2017-11-01T00:00:00.000Z2017-12-01T00:00:00.000ZVERSION_1` to compact together because `2017-11-01T00:00:00.000Z/2017-12-01T00:00:00.000Z` is the most recent time chunk. If the Coordinator has enough task slots for compaction, this policy will continue searching for the next segments and return `bar2017-10-01T00:00:00.000Z2017-11-01T00:00:00.000ZVERSION` and `bar2017-10-01T00:00:00.000Z2017-11-01T00:00:00.000ZVERSION_1`. Finally, `foo2017-09-01T00:00:00.000Z2017-10-01T00:00:00.000Z_VERSION` will be picked up even though there is only one segment in the time chunk of `2017-09-01T00:00:00.000Z/2017-10-01T00:00:00.000Z`. The search start point can be changed by setting `skipOffsetFromLatest`. If this is set, this policy will ignore the segments falling into the time chunk of (the end time of the most recent segment - `skipOffsetFromLatest`). This is to avoid conflicts between compaction tasks and realtime tasks. Note that realtime tasks have a higher priority than compaction tasks by default. Realtime tasks will revoke the locks of compaction tasks if their intervals overlap, resulting in the termination of the compaction task. For more information, see . :::info This policy currently cannot handle the situation when there are a lot of small segments which have the same interval, and their total size exceeds . If it finds such segments, it simply skips them. ::: Do clients ever contact the Coordinator service? The Coordinator is not involved in a query. Historical services never directly contact the Coordinator service. The Coordinator tells the Historical services to load/drop data via ZooKeeper, but the Historical services are completely unaware of the Coordinator. Brokers also never contact the Coordinator. Brokers base their understanding of the data topology on metadata exposed by the Historical services via ZooKeeper and are completely unaware of the Coordinator. Does it matter if the Coordinator service starts up before or after other services? No. If the Coordinator is not started up, no new segments will be loaded in the cluster and outdated segments will not be dropped. However, the Coordinator service can be started up at any time, and after a configurable delay, will start running Coordinator tasks. This also means that if you have a working cluster and all of your Coordinators die, the cluster will continue to function, it just wont experience any changes to its data topology.