You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/17 09:55:00 UTC
[jira] [Commented] (FLINK-9873) Log actual state when aborting
checkpoint due to task not running
[ https://issues.apache.org/jira/browse/FLINK-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546287#comment-16546287 ]
ASF GitHub Bot commented on FLINK-9873:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/6350
[FLINK-9873][runtime] Log task state when aborting checkpoint
## What is the purpose of the change
This PR adjusts the logging message for when a checkpoint is declined due to tasks not being ready.
We now explicitly log the current task state.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 9873
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/6350.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6350
----
commit 4dfe622fc45a2233dbba58640d6aa67be4739f86
Author: zentol <ch...@...>
Date: 2018-07-17T07:34:45Z
[FLINK-9873][runtime] Log task state when aborting checkpoint
----
> Log actual state when aborting checkpoint due to task not running
> -----------------------------------------------------------------
>
> Key: FLINK-9873
> URL: https://issues.apache.org/jira/browse/FLINK-9873
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.1, 1.6.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.2, 1.6.0
>
>
> Currently, if a checkpoint is triggered while a task s not in a RUNNING state the following message is logged:
> {code:java}
> Checkpoint triggering task {} of job {} is not being executed at the moment.{code}
> We can improve this message to include the actual task state to help diagnose problems.
> This message is also a bit ambiguous, as "being executed" could mean many things, from not "RUNNING", to not being "DEPLOYED", or to not existing at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)