aruraghuwanshi opened a new issue, #18492: URL: https://github.com/apache/druid/issues/18492
The current description is ambiguous and leads users to believe this timeout only applies while the query stays in the queue. **Current text:** > "This configured timeout is equal to MIN(Integer.MAX_VALUE, druid.server.http.maxQueryTimeout). If the value of druid.server.http.maxQueryTimeout is negative, the request is queued forever." **Issue:** The description suggests maxQueryTimeout only applies to queued queries, but it actually applies to the entire query lifecycle (queuing + execution). The timeout starts when the query is received and continues through execution - it's not reset when the query exits the queue. **Proposed fix:** Clarify that maxQueryTimeout is the maximum allowed timeout for the complete query lifecycle, not just the queuing phase. **Reference:** https://github.com/apache/druid/blob/7f9e81b8c0777c238eb51db039cc442ef74c5631/docs/operations/mixed-workloads.md#L64 -- 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]
