harinirajendran edited a comment on issue #11414:
URL: https://github.com/apache/druid/issues/11414#issuecomment-1041883825
> majority of wall clock time in the KafkaSupervisor thread was waiting on
SQL queries executing as part of the RunNotice
In our case, it wasn't the SQL queries that were causing RunNotice to take
more time. But rather, the tasks bootstrap time(~5s). @gianm's fix certainly
helped bring this down. But with time as task rollovers started getting spread
out over a few minutes, there weren't many runNotices next to each other to
coalesce, resulting in the same problem again. To bring the time for task
bootstrap down, we switched from MMs to Indexers as it doesn't involve jvm
restart for every task and that actually helped.
@jasonk000: Do you use MMs or indexers for your ingestion tasks? How long
does it take for the ingestion tasks to bootstrap in your environment?
--
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]
