GWphua commented on issue #19112:
URL: https://github.com/apache/druid/issues/19112#issuecomment-4029303004
@kfaraz
I found the fix to the problem.
It turns out that in my cluster configuration, the following config is only
provided for the Coordinator. The Overlord did not have this config.
```
druid_coordinator_asOverlord_enabled: false
```
Failure to configure this config on the Overlord is harmless before #17935.
The fact that the config is prefixed with `druid_coordinator`, and there is no
mention in the documentations, made me believe that there is no need to
consider applying this configuration on the Overlord.
After #17935, if users fail to add this config, `isStandalone()` will return
false. Users will keep seeing `Waiting for cache to finish sync with metadata
store.` in the logs, but the sync will never finish, because the Metadata Cache
Sync will is not started at all.
```
if (isStandalone()) {
segmentMetadataCache.start();
}
// How isStandalone is resolved.
private boolean isStandalone()
{
return !coordinatorOverlordServiceConfig.isEnabled();
}
```
Documentation / upgrade notes will be helpful for users looking to upgrade /
use this feature.
--
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]
