You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/08/04 03:48:00 UTC

[jira] [Commented] (FLINK-17726) Scheduler should take care of tasks directly canceled by TaskManager

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

Zhu Zhu commented on FLINK-17726:
---------------------------------

Hi [~nicholasjiang], is there any updates for the design?

> Scheduler should take care of tasks directly canceled by TaskManager
> --------------------------------------------------------------------
>
>                 Key: FLINK-17726
>                 URL: https://issues.apache.org/jira/browse/FLINK-17726
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination, Runtime / Task
>    Affects Versions: 1.11.0, 1.12.0
>            Reporter: Zhu Zhu
>            Assignee: Nicholas Jiang
>            Priority: Critical
>             Fix For: 1.12.0, 1.11.2
>
>
> JobManager will not trigger failure handling when receiving CANCELED task update. 
> This is because CANCELED tasks are usually caused by another FAILED task. These CANCELED tasks will be restarted by the failover process triggered  FAILED task.
> However, if a task is directly CANCELED by TaskManager due to its own runtime issue, the task will not be recovered by JM and thus the job would hang.
> This is a potential issue and we should avoid it.
> A possible solution is to let JobManager treat tasks transitioning to CANCELED from all states except from CANCELING as failed tasks. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)