abhishekrb19 commented on code in PR #19025: URL: https://github.com/apache/druid/pull/19025#discussion_r2835032942
########## docs/configuration/index.md: ########## @@ -1381,6 +1380,7 @@ Processing properties set on the Middle Manager are passed through to Peons. |`druid.processing.fifo`|Enables the processing queue to treat tasks of equal priority in a FIFO manner.|`true`| |`druid.processing.tmpDir`|Path where temporary files created while processing a query should be stored. If specified, this configuration takes priority over the default `java.io.tmpdir` path.|path represented by `java.io.tmpdir`| |`druid.processing.intermediaryData.storage.type`|Storage type for intermediary segments of data shuffle between native parallel index tasks. <br />Set to `local` to store segment files in the local storage of the Middle Manager or Indexer. <br />Set to `deepstore` to use configured deep storage for better fault tolerance during rolling updates. When the storage type is `deepstore`, Druid stores the data in the `shuffle-data` directory under the configured deep storage path. Druid does not support automated cleanup for the `shuffle-data` directory. You can set up cloud storage lifecycle rules for automated cleanup of data at the `shuffle-data` prefix location.|`local`| +|`druid.processing.parallelPoolInit`|Allows all merge/processing pools to be allocated in parallel on process launch. This significantly speeds up task launch times.|`false`| Review Comment: I imagine most operators would benefit from faster bootstrapping times by enabling `parallelPoolInit=true`. What do you think about leaving this config undocumented and enabling parallel initialization by default? (I noticed that some of our larger clusters currently take ~1 minute from sequential allocation) From the discussions, it seems there’s some unit test weirdness with parallel initialization. I think it'd make sense to just set this to false for those tests -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
