[
https://issues.apache.org/jira/browse/FLINK-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976712#comment-15976712
]
ASF GitHub Bot commented on FLINK-6341:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3745
Thanks for spotting the problem @WangTaoTheTonic. This is important to fix.
I think we cannot solve the problem as you've done it, because you access
actor state from outside of the actor's main thread. I think it would be better
to introduce a resource manager connection id which we can use to distinguish
whether we have to reconnect from a resource manager or whether it is an
outdated `ReconnectResourceManager` message. We can do the check then in the
handler for the `ReconnectResourceManager` message.
> 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)
