harinirajendran commented on issue #11414:
URL: https://github.com/apache/druid/issues/11414#issuecomment-1108858672
> > The log line I searched was something like `Started
ServerConnector@6e475994{HTTP/1.1, (http/1.1)}{0.0.0.0:8102}` which happens
roughly at the 4th second after the tasks start. And runNotice at the overlord
gets stuck
[here](https://github.com/confluentinc/druid/blob/0.21.0-confluent/indexing-service/src/main/java/org/apache/druid/indexing/seekablestream/supervisor/SeekableStreamSupervisor.java#L1442)
for that duration until task can respond to the `/status` call. This is my
observation. Does it make sense?
>
> @harinirajendran It does make sense. Out of curiosity -- what did you have
chatThreads set to? I wonder if your number of tasks is much higher than your
number of chat threads, and that caused the delays to compound.
@gianm : We just use the default value for chatThreads. The document says
`default == min(10, taskCount * replicas)` . So, it should be 10 in our case.
--
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]
