[
https://issues.apache.org/jira/browse/FLINK-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306498#comment-15306498
]
ASF GitHub Bot commented on FLINK-3982:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/2046
> 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)
