-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-6294] fix hang when call take() in JVM on PythonRDD #4987
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
Conversation
Test build #28487 has started for PR 4987 at commit
|
LGTM pending Jenkins. |
Test build #28487 has finished for PR 4987 at commit
|
Test FAILed. |
test this please |
Test build #28499 has started for PR 4987 at commit
|
Test build #28499 has finished for PR 4987 at commit
|
Test PASSed. |
The Thread.interrupt() can not terminate the thread in some cases, so we should not wait for the writerThread of PythonRDD. This PR also ignore some exception during clean up. cc JoshRosen mengxr Author: Davies Liu <davies@databricks.com> Closes #4987 from davies/fix_take and squashes the following commits: 4488f1a [Davies Liu] fix hang when call take() in JVM on PythonRDD (cherry picked from commit 712679a) Signed-off-by: Xiangrui Meng <meng@databricks.com>
Merged into master and branch-1.3. @davies This cannot be merged cleanly into branch-1.2. Could you send another PR for branch-1.2 and maybe branch-1.1? Thanks! |
The Thread.interrupt() can not terminate the thread in some cases, so we should not wait for the writerThread of PythonRDD. This PR also ignore some exception during clean up. cc JoshRosen mengxr Author: Davies Liu <davies@databricks.com> Closes apache#4987 from davies/fix_take and squashes the following commits: 4488f1a [Davies Liu] fix hang when call take() in JVM on PythonRDD
The Thread.interrupt() can not terminate the thread in some cases, so we should not wait for the writerThread of PythonRDD.
This PR also ignore some exception during clean up.
cc @JoshRosen @mengxr