[
https://issues.apache.org/jira/browse/FLINK-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guowei Ma updated FLINK-13426:
------------------------------
Attachment: image-2019-07-25-17-57-03-537.png
> 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
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
