You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/05/16 16:14:00 UTC
[jira] [Commented] (FLINK-17075) Add task status reconciliation
between TM and JM
[ https://issues.apache.org/jira/browse/FLINK-17075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109116#comment-17109116 ]
Till Rohrmann commented on FLINK-17075:
---------------------------------------
As a band aid I would suggest to add a small number of retries and then to fail fatally if we could not update the task state. This would, at least, not leave the cluster in an unusable state.
> Add task status reconciliation between TM and JM
> ------------------------------------------------
>
> Key: FLINK-17075
> URL: https://issues.apache.org/jira/browse/FLINK-17075
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Till Rohrmann
> Priority: Critical
> Fix For: 1.11.0, 1.10.2
>
>
> In order to harden the TM and JM communication I suggest to let the {{TaskExecutor}} send the task statuses back to the {{JobMaster}} as part of the heartbeat payload (similar to FLINK-11059). This would allow to reconcile the states of both components in case that a status update message was lost as described by a user on the ML.
> https://lists.apache.org/thread.html/ra9ed70866381f0ef0f4779633346722ccab3dc0d6dbacce04080b74e%40%3Cuser.flink.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)