[
https://issues.apache.org/jira/browse/FLINK-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321485#comment-17321485
]
Flink Jira Bot commented on FLINK-13426:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> TaskExecutor uses the wrong Registrationid in the heartbeat with RM.
> --------------------------------------------------------------------
>
> Key: FLINK-13426
> URL: https://issues.apache.org/jira/browse/FLINK-13426
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.8.1, 1.9.0
> Reporter: Guowei Ma
> Priority: Minor
> Labels: stale-minor
> Attachments: image-2019-07-25-17-57-03-537.png
>
>
> 1. First-time TaskExecutor register to rm successfully. If it fails to send
> SlotReport to SlotMaanger, TaskExecutor will reconnect to RM again. However,
> TaskExecutor still uses the old registration id in the
> EstablishedResourceManagerConnection.
> 2. Second-time TaskExecutor registers to rm successfully and gets a new
> registration id.
> 3. First-round and second-round has a race condition. Since that the task
> executor maybe use the old registration id in heartbeat with rm.
>
> !image-2019-07-25-17-57-03-537.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
