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 2021/05/05 13:56:00 UTC

[jira] [Updated] (FLINK-16562) Handle JobManager termination future in place

     [ https://issues.apache.org/jira/browse/FLINK-16562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-16562:
----------------------------------
    Fix Version/s:     (was: 1.14.0)

> Handle JobManager termination future in place
> ---------------------------------------------
>
>                 Key: FLINK-16562
>                 URL: https://issues.apache.org/jira/browse/FLINK-16562
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Zili Chen
>            Priority: Major
>              Labels: auto-unassigned
>
> After FLINK-11843 {{Dispatcher}} becomes a {{PermanentlyFencedRpcEndpoint}} and will be created as different instance in difference leader epoch. Thus, we don't have {{jobManagerTerminationFutures}} crosses multiple leader epoch that should be handled. Given the truth, we can remove {{jobManagerTerminationFutures}} field in {{Dispatcher}} and handle those futures in place, which will simplify the code and helps on further refactoring.
> CC [~trohrmann]
> I will create a branch later this week.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)