[
https://issues.apache.org/jira/browse/FLINK-9493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520248#comment-16520248
]
vinoyang commented on FLINK-9493:
---------------------------------
[~azagrebin] That's all right. Generally, if a issue was assigned to someone,
that means he would fix this (few guys would mark Status as 'In Progress'). If
you want to do, you could ask the progress about it. If he did not start, he
would release the assignee then you can assign it to yourself. :)
> 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)
