You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sachin Goel (JIRA)" <ji...@apache.org> on 2015/11/14 12:05:10 UTC

[jira] [Assigned] (FLINK-3000) Add ShutdownHook to YARN CLI to prevent lingering sessions

     [ https://issues.apache.org/jira/browse/FLINK-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sachin Goel reassigned FLINK-3000:
----------------------------------

    Assignee: Sachin Goel

> Add ShutdownHook to YARN CLI to prevent lingering sessions
> ----------------------------------------------------------
>
>                 Key: FLINK-3000
>                 URL: https://issues.apache.org/jira/browse/FLINK-3000
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN Client
>    Affects Versions: 0.10
>            Reporter: Ufuk Celebi
>            Assignee: Sachin Goel
>             Fix For: 0.10.1
>
>
> Submitting a job via
> {code}
> bin/flink run -m yarn-cluster ...
> {code}
> and terminating the client can lead to lingering YARN sessions allocating cluster resources.
> This was reported by a user.
> {code}
> 1) One starts a flink job in the yarn mode
> 2) He sees that containers are not allocated since cluster is busy
> 3) Presses Ctrl+C
> 4) An “empty” flink session remains in the cluster although the Flink didn’t print that “you can track your application on the X URL”
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)