flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-3000) Add ShutdownHook to YARN CLI to prevent lingering sessions
Date Wed, 25 Nov 2015 15:42:11 GMT

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

Robert Metzger resolved FLINK-3000.
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.10.1)
                   1.0.0

Resolved for 1.0.0 in http://git-wip-us.apache.org/repos/asf/flink/commit/aad99f25

Thank you for the fix!

> 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.0
>            Reporter: Ufuk Celebi
>            Assignee: Sachin Goel
>             Fix For: 1.0.0
>
>
> 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)

Mime
View raw message