Jackie-Jiang commented on PR #11496: URL: https://github.com/apache/pinot/pull/11496#issuecomment-1722561659
@jasperjiaguo This is resource starvation instead of deadlock then. During your investigation do you see closing all connections necessary? Ideally we want to only close the connection that throws exception for the following reasons: - Closing all connections will fail all on-the-fly queries - Some connections might not request lots of memory (data not evenly distributed, expensive query only hits subset of servers) - After releasing the connection throwing the exception, other connections might recover -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
