From 6697f3a62b59c0f403da9bd9c784b3f29b0950ee Mon Sep 17 00:00:00 2001 From: Jordan Pittier Date: Wed, 7 Jun 2017 19:24:42 +0200 Subject: [PATCH] [Doc]Update configuration/historical.md: correct default numBootstrapThreads value (#4376) According to https://github.com/druid-io/druid/blob/4ace65a2af7c92bbd3b2fa56ebbc3cbf05e7730a/server/src/main/java/io/druid/segment/loading/SegmentLoaderConfig.java#L81 if numBootstrapThreads is not set, it default to numLoadingThreads. --- docs/content/configuration/historical.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuration/historical.md b/docs/content/configuration/historical.md index 26f268af777..d97c3e294f0 100644 --- a/docs/content/configuration/historical.md +++ b/docs/content/configuration/historical.md @@ -36,7 +36,7 @@ The historical node uses several of the global configs in [Configuration](../con |`druid.segmentCache.infoDir`|Historical nodes keep track of the segments they are serving so that when the process is restarted they can reload the same segments without waiting for the Coordinator to reassign. This path defines where this metadata is kept. Directory will be created if needed.|${first_location}/info_dir| |`druid.segmentCache.announceIntervalMillis`|How frequently to announce segments while segments are loading from cache. Set this value to zero to wait for all segments to be loaded before announcing.|5000 (5 seconds)| |`druid.segmentCache.numLoadingThreads`|How many segments to load concurrently from from deep storage.|1| -|`druid.segmentCache.numBootstrapThreads`|How many segments to load concurrently from local storage at startup.|1| +|`druid.segmentCache.numBootstrapThreads`|How many segments to load concurrently from local storage at startup.|Same as numLoadingThreads| ### Query Configs