flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-3982) Multiple ResourceManagers register at JobManager in standalone HA mode
Date Mon, 30 May 2016 10:31:13 GMT

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

Maximilian Michels closed FLINK-3982.
-------------------------------------
    Resolution: Fixed

Fixed with 1212b6d3ff676877f84a51e9c849f9e484297947

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

Mime
View raw message