You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/27 20:44:12 UTC
[jira] [Commented] (FLINK-3982) Multiple ResourceManagers register
at JobManager in standalone HA mode
[ https://issues.apache.org/jira/browse/FLINK-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304740#comment-15304740 ]
ASF GitHub Bot commented on FLINK-3982:
---------------------------------------
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
----
> Multiple ResourceManagers register at JobManager in standalone HA mode
> ----------------------------------------------------------------------
>
> Key: FLINK-3982
> URL: https://issues.apache.org/jira/browse/FLINK-3982
> Project: Flink
> Issue Type: Bug
> Components: ResourceManager
> Affects Versions: 1.1.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 1.1.0
>
>
> 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 the ResourceManager. Other ResourceManager implementations may also run independently of the JobManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)