This message was deleted.
# troubleshooting
s
This message was deleted.
k
No they should not be any issues. MSQE uses ingestion tasks to process the data. Can you check if you are using a different tier for peon tasks. 'druid.lookup.lookupTier' is used to control that.
https://druid.apache.org/docs/latest/querying/lookups.html#configuration has the configurations that are set via the middle manager
l
I have these configs set for all services
Copy code
druid_lookup_lookupTierIsDatasource: "false"
  druid_lookup_lookupTier: __default
I can see they’re the default values. Not sure why they were explicitly defined in the past.
Copy code
2023-02-14T16:33:49,202 INFO [main] org.apache.druid.cli.CliMiddleManager - * druid.lookup.enableLookupSyncOnStartup: false
2023-02-14T16:33:49,203 INFO [main] org.apache.druid.cli.CliMiddleManager - * druid.lookup.lookupTier: __default
2023-02-14T16:33:49,203 INFO [main] org.apache.druid.cli.CliMiddleManager - * druid.lookup.lookupTierIsDatasource: false
k
Aah the ingestion is not waiting for lookups to load. 'enableLookupSyncOnStartup' is false.
druid.lookup.enableLookupSyncOnStartup Enable the lookup synchronization process with Coordinator on startup. The queryable processes will fetch and load the lookups from the Coordinator instead of waiting for the Coordinator to load the lookups for them. Users may opt to disable this option if there are no lookups configured in the cluster. true
l
Setting
druid.lookup.enableLookupSyncOnStartup: true
fixed, thanks @Karan Kumar I wasn’t expecting this one to be the problem as my queries were working fine and my lookups are periodically refreshed from external sources, so the ‘sync on startup’ wasn’t looking like a solution here.
🙌 1