[
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-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> 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)
