4.9 KiB
| id | title |
|---|---|
| historical | Historical Process |
Configuration
For Apache Druid Historical Process Configuration, see Historical Configuration.
For basic tuning guidance for the Historical process, see Basic cluster tuning.
HTTP endpoints
For a list of API endpoints supported by the Historical, please see the Service status API reference.
Running
org.apache.druid.cli.Main server historical
Loading and serving segments
Each Historical process copies or "pulls" segment files from Deep Storage to local disk in an area called the segment cache. Set the druid.segmentCache.locations to configure the size and location of the segment cache on each Historical process. See Historical general configuration.
See the Tuning Guide for more information.
The Coordinator controls the assignment of segments to Historicals and the balance of segments between Historicals. Historical processes do not communicate directly with each other, nor do they communicate directly with the Coordinator. Instead, the Coordinator creates ephemeral entries in Zookeeper in a load queue path. Each Historical process maintains a connection to Zookeeper, watching those paths for segment information.
For more information about how the Coordinator assigns segments to Historical processes, see Coordinator.
When a Historical process detects a new entry in the Zookeeper load queue, it checks its own segment cache. If no information about the segment exists there, the Historical process first retrieves metadata from Zookeeper about the segment, including where the segment is located in Deep Storage and how it needs to decompress and process it.
For more information about segment metadata and Druid segments in general, see Segments.
After a Historical process pulls down and processes a segment from Deep Storage, Druid advertises the segment as being available for queries from the Broker. This announcement by the Historical is made via Zookeeper, in a served segments path.
For more information about how the Broker determines what data is available for queries, please see Broker.
To make data from the segment cache available for querying as soon as possible, Historical services search the local segment cache upon startup and advertise the segments found there.
Loading and serving segments from cache
The segment cache uses memory mapping. The cache consumes memory from the underlying operating system so Historicals can hold parts of segment files in memory to increase query performance at the data level. The in-memory segment cache is affected by the size of the Historical JVM, heap / direct memory buffers, and other processes on the operating system itself.
At query time, if the required part of a segment file is available in the memory mapped cache or "page cache", the Historical re-uses it and reads it directly from memory. If it is not in the memory-mapped cache, the Historical reads that part of the segment from disk. In this case, there is potential for new data to flush other segment data from memory. This means that if free operating system memory is close to druid.server.maxSize, the more likely that segment data will be available in memory and reduce query times. Conversely, the lower the free operating system memory, the more likely a Historical is to read segments from disk.
Note that this memory-mapped segment cache is in addition to other query-level caches.
Querying segments
Please see Querying for more information on querying Historical processes.
A Historical can be configured to log and report metrics for every query it services.