walterddr commented on issue #11072: URL: https://github.com/apache/pinot/issues/11072#issuecomment-1642337396
yes we should do a framegraph dump and see what's the time spent during the tearDown() process (e.g. is it on server executor or mailbox service or the scheduler async wait. once we ident we should be able to figure out which step is stuck cleaning stuff up. The fact that it only happens to the QueryRunnerTest but not the ResourceBasedQueriesTest is also interesting to see which query actually is causing the tear down to be slow -- 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
