-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-11823][SQL] Fix flaky JDBC cancellation test in HiveThriftBinaryServerSuite #10425
Conversation
/cc @marmbrus @shaneknapp |
Test build #48145 has finished for PR 10425 at commit
|
logInfo("HiveThriftServer2 stopped") | ||
try { | ||
stopThriftServer() | ||
logInfo("HiveThriftServer2 stopped") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this log?
LGTM. |
I'm going to merge this into master and branch-1.6. We can consider a more principled fix, such as using some sort of timed-sleep UDF, in case this turns out to be flaky. My main motivation in this change was to fix the process leaks that were caused by the hour+ timeouts that this test used to experience. |
…ryServerSuite This patch fixes a flaky "test jdbc cancel" test in HiveThriftBinaryServerSuite. This test is prone to a race-condition which causes it to block indefinitely with while waiting for an extremely slow query to complete, which caused many Jenkins builds to time out. For more background, see my comments on #6207 (the PR which introduced this test). Author: Josh Rosen <[email protected]> Closes #10425 from JoshRosen/SPARK-11823. (cherry picked from commit 2235cd4) Signed-off-by: Josh Rosen <[email protected]>
Looks like this test is still leading to hangs in Jenkins. Given that I thought this patch would change those hangs into test timeouts/failures, I wonder whether the |
This patch fixes a flaky "test jdbc cancel" test in HiveThriftBinaryServerSuite. This test is prone to a race-condition which causes it to block indefinitely with while waiting for an extremely slow query to complete, which caused many Jenkins builds to time out.
For more background, see my comments on #6207 (the PR which introduced this test).