This message was deleted.

Hi Sachidananda, I am the author of that query so I can shed some light on it. The

sys

schema tables are virtual tables that provide a SQL queryable view into Druid's metadata (as cached on the broker). You can read more about them here: https://druid.apache.org/docs/latest/querying/sql-metadata-tables.html . The web console uses these tables extensively (incidentally if you have any more questions about the web console please post them in the #C030K0Z7S1Z channel). You can build your own queries on top of the

sys

tables for whatever monitoring you might want to do. Every web console table that is powered by a sys table provides a way for you to "open the query" in the Query view.

Thanks a lot @Vadim for the insights

Task info comes from the overload but the SQL processing itself is done on the broker

can this cause overlord to go down if there are too many tasks? And the ui refresh setting is set at 10 seconds? As i observerd some overlord cpu utilization for overlord went high and leader shifted form one to other while loading tasks page but not sure

As I said above you should update to 24.0

ok sure @Vadim thanks for the inputs