You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by mxm <gi...@git.apache.org> on 2016/05/27 20:43:46 UTC

[GitHub] flink pull request: [FLINK-3982] let only ResourceManager of leadi...

GitHub user mxm opened a pull request:

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

    [FLINK-3982] let only ResourceManager of leading JobManager register

    In HA mode, multiple ResourceManagers may register at the leading
    JobManager. They register one after another at the JobManager. The last
    registering ResourceManager stays registered with the JobManager. This
    only applies to Standalone mode and doesn't affect functionality.
    
    To prevent duplicate registration for the standalone ResourceManager,
    the easiest solution is to only start registration when the leading
    JobManager runs in the same ActorSystem as theResourceManager. Other
    ResourceManager implementations may also run independently of the
    JobManager.

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

    $ git pull https://github.com/mxm/flink FLINK-3982

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

    https://github.com/apache/flink/pull/2046.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 #2046
    
----
commit 09cbb90d2a93ba0c9efb82e16f421641c10fec32
Author: Maximilian Michels <mx...@apache.org>
Date:   2016-05-27T19:03:04Z

    [FLINK-3982] let only ResourceManager of leading JobManager register
    
    In HA mode, multiple ResourceManagers may register at the leading
    JobManager. They register one after another at the JobManager. The last
    registering ResourceManager stays registered with the JobManager. This
    only applies to Standalone mode and doesn't affect functionality.
    
    To prevent duplicate registration for the standalone ResourceManager,
    the easiest solution is to only start registration when the leading
    JobManager runs in the same ActorSystem as theResourceManager. Other
    ResourceManager implementations may also run independently of the
    JobManager.

commit 30e58fdcdbbf211b1c0908bb2467464c1f83f07c
Author: Maximilian Michels <mx...@apache.org>
Date:   2016-05-27T19:33:29Z

    correct entity in String

----


---
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.
---

[GitHub] flink pull request: [FLINK-3982] let only ResourceManager of leadi...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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.
---