[
https://issues.apache.org/jira/browse/FLINK-26650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506939#comment-17506939
]
Piotr Nowojski edited comment on FLINK-26650 at 3/15/22, 2:36 PM:
------------------------------------------------------------------
Thanks for noticing the issue [~yunta]. Checkpoint trigger failures is a super
set of "not all tasks are started". I think not all trigger failures should be
treated the same way.
was (Author: pnowojski):
Checkpoint trigger failures is a super set of "not all tasks are started". I
think not all trigger failures should be treated the same way.
> Avoid to print stack trace for checkpoint trigger failure if not all tasks
> are started
> --------------------------------------------------------------------------------------
>
> Key: FLINK-26650
> URL: https://issues.apache.org/jira/browse/FLINK-26650
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Yun Tang
> Assignee: Yun Tang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0, 1.16.0
>
>
> This ticket is somehow like FLINK-22117. After FLINK-26049, we would always
> print the stack trace of fail-to-trigger checkpoint, which is annoying at the
> beginning of flink jobs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
