[
https://issues.apache.org/jira/browse/FLINK-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17043:
-----------------------------------
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.
> Putting more information into accounting when failing a job in FailureManager
> -----------------------------------------------------------------------------
>
> Key: FLINK-17043
> URL: https://issues.apache.org/jira/browse/FLINK-17043
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Affects Versions: 1.13.0
> Reporter: Congxian Qiu
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Currently, we only fail the job when we received continues
> "CHECKPOINT_DECLINED" message, but ignored the
> "timeout"/"task_failure"/"task_checkpoint_failure"/"finalize_checkpoint_failure"
> and so on.
> In my opinion, we should put some checkpoint failure reason above into
> account when failing a job (not only the "CHECKPOINT_DECLINED" reason"
> This issue is inspired by a [user mail
> list|[http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Making-job-fail-on-Checkpoint-Expired-tt34051.html]],
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
