[ https://issues.apache.org/jira/browse/FLINK-22069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322176#comment-17322176 ]
Stephan Ewen edited comment on FLINK-22069 at 4/15/21, 1:23 PM: ---------------------------------------------------------------- There is one that doesn't yet seem to be fixed that I found really bad during debugging: logging the full exception stack trace when a checkpoint cannot be triggered due to the fact that some tasks are still starting up: FLINK-22229 It happens during almost every startup, is often unavoidable, and is a completely fine and expected situation. The stack trace makes it look scary. I would say it is not a blocker, but we should try hard to get that fix in. was (Author: stephanewen): There is one that doesn't yet seem to be fixed that I found really bad during debugging: logging the full exception stack trace when a checkpoint cannot be triggered due to the fact that some tasks are still starting up: FLINK-22229 It happens during almost every startup, is often unavoidable, and is a completely fine and expected situation. The stack trace makes it look scary. I would say it is not a blocker, but we should try and fix this. > Check Log Pollution for 1.13 release > ------------------------------------ > > Key: FLINK-22069 > URL: https://issues.apache.org/jira/browse/FLINK-22069 > Project: Flink > Issue Type: Bug > Components: Runtime / Coordination > Reporter: Stephan Ewen > Assignee: Chesnay Schepler > Priority: Blocker > Labels: pull-request-available > Fix For: 1.13.0 > > > We should check for log pollution and confusing log lines before the release. -- This message was sent by Atlassian Jira (v8.3.4#803005)