kfaraz commented on code in PR #17935: URL: https://github.com/apache/druid/pull/17935#discussion_r2054606916
########## docs/configuration/index.md: ########## @@ -925,6 +925,7 @@ These Coordinator static configurations can be defined in the `coordinator/runti |--------|-----------|-------| |`druid.manager.config.pollDuration`|How often the manager polls the config table for updates.|`PT1M`| |`druid.manager.segments.pollDuration`|The duration between polls the Coordinator does for updates to the set of active segments. Generally defines the amount of lag time it can take for the Coordinator to notice new segments.|`PT1M`| +|`druid.manager.segments.useCache`|(Experimental) Denotes the usage mode of the segment metadata cache. The cache provides a performance improvement over the polling mechanism currently employed by the Coordinator by retrieving payloads of only updated segments. Possible cache modes are: (a) `never`: Cache is disabled. (b) `always`: Reads are always done from the cache. Service start-up will be blocked until cache has synced with the metadata store at least once. Transactions will block until cache has synced with the metadata store at least once after becoming leader. (c) `ifSynced`: Reads are done from the cache only if it has already synced with the metadata store. This mode does not block service start-up but blocks read transactions.|`never`| Review Comment: The config description was mostly just copied over from the Overlord section. I will update it so that it makes sense for the Coordinator. -- 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]
