The unified Druid Console was introduced in Imply 2.9 / Druid 0.14. This console is based on API calls to system schema tables, which were introduced in Druid 0.13.
In a cluster with a large number of segments (~1 million) and/or large number of datasources, the current Druid console response can be less than snappy. There are a few improvements in the works to address this (e.g. https://github.com/apache/druid/pull/10909, https://github.com/apache/druid/pull/11008). There are two things that can be done at the moment:
1. Set druid.sql.planner.metadataSegmentCacheEnable=true in the broker runtime.properties. Please note this setting will create more memory pressure on the brokers, so should be tested in a staging environment first.
2. Upgrade to Imply 3.4 / Druid 0.19, which includes PR #9883 to remove the payload from sys.segments table.
If the above don't improve the loading time of the console to acceptable levels, there is a fallback option to allow the Datasources tab of the console to function on coordinator APIs and the Ingestion tab to function on the overlord APIs instead of the sys tables:
2. In the JS console, run the command:
The console will reload and run in coordinator mode until removed via the command below or by 'clearing stored data') in the browser.
The command above will also disable the auto-refresh in the Segments tab, which will still be running on the sys.segments table:
**Note that the "Load Data" and "Query" tabs will not be available in this mode.
3. To undo, run this command in the JS console: