[
https://issues.apache.org/jira/browse/FLINK-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-9873.
-----------------------------------
Resolution: Fixed
master: 9e0a4b5403bb2a5cc98502dd9ce0c576a915c31b
1.6: 87cb185b5d270f1cc6f05756fb25d00c5eaf5ff7
1.5: aa770ba6f325b85c7242e535d45a6080d2703232
> 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.0, 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)
