You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/04/28 16:13:04 UTC

[jira] [Resolved] (FLINK-6341) JobManager can go to definite message sending loop when TaskManager registered

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

Till Rohrmann resolved FLINK-6341.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Fixed via 238383926b762c1d47159a2b4dabe8fd59777307

> JobManager can go to definite message sending loop when TaskManager registered
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-6341
>                 URL: https://issues.apache.org/jira/browse/FLINK-6341
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>            Reporter: Tao Wang
>            Assignee: Tao Wang
>             Fix For: 1.3.0
>
>
> When TaskManager register to JobManager, JM will send a "NotifyResourceStarted" message to kick off Resource Manager, then trigger a reconnection to resource manager through sending a "TriggerRegistrationAtJobManager".
> When the ref of resource manager in JobManager is not None and the reconnection is to same resource manager, JobManager will go to a infinite message sending loop which will always sending himself a "ReconnectResourceManager" every 2 seconds.
> We have already observed that phonomenon. More details, check how JobManager handles `ReconnectResourceManager`.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)