[
https://issues.apache.org/jira/browse/FLINK-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980686#comment-15980686
]
ASF GitHub Bot commented on FLINK-6341:
---------------------------------------
Github user WangTaoTheTonic commented on the issue:
https://github.com/apache/flink/pull/3745
@tillrohrmann What problem it will bring if we access
`currentResourceManager` from another thread? It is a variable in JobManager
and can be shared across multi threads, right? The new added code just read it
and there's no cocurrency problem coming, i think.
> 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)
