[
https://issues.apache.org/jira/browse/FLINK-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214575#comment-14214575
]
ASF GitHub Bot commented on FLINK-1154:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/incubator-flink/pull/208#issuecomment-63295089
I am not sure that the `stop()` function should go into the TaskManager
interface. Until now, the TaskManager was not assumed to run in its own
proccess.
I think putting this into the `TaskManagerRunner` would make more sense.
> YarnTaskManagerRunner does not shut down
> ----------------------------------------
>
> Key: FLINK-1154
> URL: https://issues.apache.org/jira/browse/FLINK-1154
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Reporter: Till Rohrmann
> Assignee: Robert Metzger
>
> The YarnClient does not shut down the YarnTaskManagerRunner when the client
> receives a stop command or is terminated. This causes a resource leak on the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
