[
https://issues.apache.org/jira/browse/FLINK-16562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16562:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> 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.20.1#820001)
