This message was deleted.

I tried with refresh interval none that also doesn’t work

I believe this happens when you are trying to display too many tasks in the UI. You can control the time frame for which task logs are stored and therefore reduce the number of tasks displayed. Take a look at Task Log configuration particularly regarding retention settings. By setting

druid.indexer.logs.kill.enabled=True

and an appropriate duration to retain with

druid.indexer.logs.kill.durationToRetain

specified in milliseconds.

if you are getting 502/504 that timeout is likely happening in some network service (like ELB) that sits between the console (ui) and Druid. It is important to note that in Druid 24.0 there were a number of improvements made to the speed of that API.

Thanks @Vadim, I knew I was missing one!

BTW this: https://github.com/apache/druid/pull/12404 is the change I was referring to that made the task fetching much much better/faster. Honestly, I believe it is worth upgrading for that change alone. Even if you generally do not encounter an issue with having too many tasks (and slow task APIs as a result) you might find yourself in that situation due to some issue completely outside of Druid. Maybe one day you wake up and there is a network connectivity issue between Druid <> Kafka and the supervisor is continuously restarting tasks that fail quickly. The console would load slowly when you need it most. The PR linked above is a game changer.

Thanks @Sergio Ferragut and@Vadim for the quick responses Indeed it looks like we have ngnix in front of druid-router.. will try and increase the timeout there Thanks for inof regarding 24.0.0 that is another reasin to plan our upgrade

Which version did this land on? 24.0.0?

https://github.com/apache/druid/pull/12404 was 24.0