gianm commented on issue #12262: URL: https://github.com/apache/druid/issues/12262#issuecomment-1183690589
> I think these are both artifacts of not using async http handling so that we could manage the queue of query requests ourselves? I believe async http request handling for queries would be actually required as long as we want to maintain the current HTTP request API model for interactive queries. @clintropolis I agree that server stuff does need to be "more async", although it may take a different form than converting our existing protocol to use the Jetty async stuff. There's two things I'd keep in mind when designing what to do next: - We don't have to keep the current request/response structure. If it helps, we can change to a protocol that allows multiplexing of multiple requests over the same connection. - Queues can't grow forever. Async handling allows the queue to grow bigger than request-per-thread handling, but there is still a limit, and we still need to have some reasonable behavior around those limits. -- 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]
