AmatyaAvadhanula commented on issue #13692: URL: https://github.com/apache/druid/issues/13692#issuecomment-1396563950
1. Could you also please share how long your coordinator runs take and which duty takes the most time as well? (`coordinator/time` metric) 2. Which cost balancer strategy does the cluster use and what is the coordinator dynamic config? 3. How do the sums of the metrics `ingest/segment/count` and `segment/assigned/count` look like over intervals of 5 minutes? > 2nd question is even if a task does not complete within the completionTimeout window I am assuming the segment isnt just dropped, since internally in the logs the task is marked as successfull but the segment will likely not be served for queries until the handoff internally is completed by the coordinator -> historical (meaning the peon will not serve requests either for that segment as the task has been terminated once completionTimeout window has elapsed). Is this a correct assumption? Yes, the segments aren't dropped and will eventually be served by the historicals -- 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]
