flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink pull request #3981: [FLINK-6646] [yarn] Let YarnJobManager delete Yarn...
Date Wed, 24 May 2017 16:13:42 GMT
GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/3981

    [FLINK-6646] [yarn] Let YarnJobManager delete Yarn application files

    Before the YarnClusterClient decided when to delete the Yarn application files.
    This is problematic because the client does not know whether a Yarn application
    is being restarted or terminated. Due to this the files where always deleted. This
    prevents Yarn from restarting a failed ApplicationMaster, effectively thwarting
    Flink's HA capabilities.
    
    The PR changes the behaviour such that the YarnJobManager deletes the Yarn files
    if it receives a StopCluster message. That way, we can be sure that the yarn files
    are deleted only iff the cluster is intended to be shut down.
    
    cc @rmetzger 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink fixYarnSession

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3981.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3981
    
----
commit 72ce39a1752cc19669f003b70cc2708852a06ac5
Author: Till Rohrmann <trohrmann@apache.org>
Date:   2017-05-24T15:59:51Z

    [FLINK-6646] [yarn] Let YarnJobManager delete Yarn application files
    
    Before the YarnClusterClient decided when to delete the Yarn application files.
    This is problematic because the client does not know whether a Yarn application
    is being restarted or terminated. Due to this the files where always deleted. This
    prevents Yarn from restarting a failed ApplicationMaster, effectively thwarting
    Flink's HA capabilities.
    
    The PR changes the behaviour such that the YarnJobManager deletes the Yarn files
    if it receives a StopCluster message. That way, we can be sure that the yarn files
    are deleted only iff the cluster is intended to be shut down.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message