You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/10/13 08:48:01 UTC
[jira] [Commented] (SPARK-22272) killing task may cause the
executor progress hang because of the JVM bug
[ https://issues.apache.org/jira/browse/SPARK-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203199#comment-16203199 ]
Sean Owen commented on SPARK-22272:
-----------------------------------
This is long since fixed in the JDK though. Does spark even need to work around it, or could it?
> killing task may cause the executor progress hang because of the JVM bug
> ------------------------------------------------------------------------
>
> Key: SPARK-22272
> URL: https://issues.apache.org/jira/browse/SPARK-22272
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.1.1
> Environment: java version "1.7.0_75"
> hadoop version 2.5.0
> Reporter: roncenzhao
> Attachments: 26883.jstack, screenshot-1.png, screenshot-2.png
>
>
> JVM bug: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8132693
> We kill the task using 'Thread.interrupt()' and the ShuffleMapTask use nio to merge all partitions files when 'spark.file.transferTo' is true(default), so it may cause the jvm bug.
> When the driver send one task to this bad executor, the task will never run and as a result the job will hang forever without handling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org