You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/03/15 12:24:00 UTC

[jira] [Comment Edited] (FLINK-26650) Avoid to print stack trace for checkpoint trigger failure if not all tasks are started

    [ https://issues.apache.org/jira/browse/FLINK-26650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506806#comment-17506806 ] 

Yun Tang edited comment on FLINK-26650 at 3/15/22, 12:23 PM:
-------------------------------------------------------------

cc [~pnowojski], [~gaoyunhaii]


was (Author: yunta):
cc [~pnowojski]

> 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)