You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2022/07/21 09:09:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Wenchen Fan updated SPARK-38916:
--------------------------------
    Fix Version/s:     (was: 3.2.2)

> 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
>            Assignee: Wei Xue
>            Priority: Minor
>             Fix For: 3.3.0
>
>
> 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.10#820010)

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