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 R. Owen (Jira)" <ji...@apache.org> on 2022/04/16 19:03:00 UTC

[jira] [Commented] (SPARK-38916) Tasks not killed caused by race conditions between killTask() and launchTask()

    [ https://issues.apache.org/jira/browse/SPARK-38916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523174#comment-17523174 ] 

Sean R. Owen commented on SPARK-38916:
--------------------------------------

OK, how would we resolve this though?

> Tasks not killed caused by race conditions between killTask() and launchTask()
> ------------------------------------------------------------------------------
>
>                 Key: SPARK-38916
>                 URL: https://issues.apache.org/jira/browse/SPARK-38916
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 3.2.1
>            Reporter: Wei Xue
>            Priority: Minor
>
> Sometimes when the scheduler tries to cancel a task right after it launches that task on the executor, the KillTask and LaunchTask events can come in a reversed order, causing the task to escape the kill-task signal and finish "secretly". And those tasks even show as an un-launched task in Spark UI.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org