[
https://issues.apache.org/jira/browse/FLINK-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976609#comment-15976609
]
ASF GitHub Bot commented on FLINK-6341:
---------------------------------------
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/flink/pull/3745
[FLINK-6341]Don't let JM fall into infinite loop
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`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/flink FLINK-6341
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3745.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 #3745
----
commit 8eb4dd42a71d9830c91b3db824e3133ce3d35c08
Author: WangTaoTheTonic <wangtao...@huawei.com>
Date: 2017-04-20T12:28:10Z
Don't let JM fall into infinite loop
----
> 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
>
> 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)
