maytasm commented on PR #18148: URL: https://github.com/apache/druid/pull/18148#issuecomment-5515963329
@jtuglu1 The per-segment timeout starts counting at submit time (ForwardingQueryProcessingPool.submitRunnerTask wraps the future at submit time). So time spent queued in the historical processing pool counts against the per-segment time. This can timeout fast queries if it's blocked behind slow queries (the processing pools were saturated by expensive queries). Is there any reason we don't start counting when segment is actually processing (instead of submitted) -- 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]
