[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
]
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)
[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
]
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)
[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
]
Flink Jira Bot updated FLINK-16562:
---
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, 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: Minor
> Labels: auto-deprioritized-major, 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)
[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
]
Flink Jira Bot updated FLINK-16562:
---
Labels: auto-unassigned stale-major (was: 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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, 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: Major
> Labels: auto-unassigned, stale-major
>
> 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)
[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)
[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
]
Dawid Wysakowicz updated FLINK-16562:
-
Fix Version/s: (was: 1.13.0)
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
> Fix For: 1.14.0
>
>
> 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)
[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
]
Flink Jira Bot updated FLINK-16562:
---
Labels: auto-unassigned (was: stale-assigned)
> 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
>Assignee: Zili Chen
>Priority: Major
> Labels: auto-unassigned
> Fix For: 1.13.0
>
>
> 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)
[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
]
Flink Jira Bot updated FLINK-16562:
---
Labels: stale-assigned (was: )
> 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
>Assignee: Zili Chen
>Priority: Major
> Labels: stale-assigned
> Fix For: 1.13.0
>
>
> 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)
[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
]
Robert Metzger updated FLINK-16562:
---
Fix Version/s: (was: 1.12.0)
1.13.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
>Assignee: Zili Chen
>Priority: Major
> Fix For: 1.13.0
>
>
> 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)
