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

Posted to issues@flink.apache.org by "Andrey Zagrebin (JIRA)" <ji...@apache.org> on 2018/06/22 10:15:00 UTC

[jira] [Comment Edited] (FLINK-9493) Forward exception when releasing a TaskManager at the SlotPool

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

Andrey Zagrebin edited comment on FLINK-9493 at 6/22/18 10:14 AM:
------------------------------------------------------------------

[~yanghua], sorry, there was no started progress


was (Author: azagrebin):
[~yanghua], sorry, I thought there was no started progress

> Forward exception when releasing a TaskManager at the SlotPool
> --------------------------------------------------------------
>
>                 Key: FLINK-9493
>                 URL: https://issues.apache.org/jira/browse/FLINK-9493
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Andrey Zagrebin
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.6.0, 1.5.1
>
>
> We should add a cause when calling {{SlotPool#releaseTaskManager}} because the release operation can be the final root cause of the job failure. Currently, we create a generic exception which hides the true reason for the release operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)