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

Flink Jira Bot updated FLINK-19860:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

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.


> Consider skipping restart and traverse regions which are already being 
> restarted in RestartPipelinedRegionFailoverStrategy
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-19860
>                 URL: https://issues.apache.org/jira/browse/FLINK-19860
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Andrey Zagrebin
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
>  Original 
> [discussion|https://github.com/apache/flink/pull/13749#pullrequestreview-516385846].
>  Follow-up for FLINK-19712. Draft 
> [branch|https://github.com/azagrebin/flink/tree/FLINK-19860].
> This means not outputting executions of regions, where all executions are in 
> CREATED (or also FAILED, CANCELING, CANCELED) state, and their dependents in 
> RestartPipelinedRegionFailoverStrategy, except the region with the failed 
> execution at hand.



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

Reply via email to