You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/04/27 15:07:12 UTC

[jira] [Closed] (FLINK-3824) ResourceManager may repeatedly connect to outdated JobManager in HA mode

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

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

Fixed with 7ec1300a740e9b8e1eb595bc15e752a167592e00.

> ResourceManager may repeatedly connect to outdated JobManager in HA mode
> ------------------------------------------------------------------------
>
>                 Key: FLINK-3824
>                 URL: https://issues.apache.org/jira/browse/FLINK-3824
>             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
>
>
> When the ResourceManager receives a new leading JobManager via the LeaderRetrievalService it tries to register with this JobManager until connected. If during registration a new leader gets elected, the ResourceManager may still repeatedly try to register with the old one. This doesn't affect the registration with the new JobManager but leaves error messages in the log file and may process unnecessary messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)