rkhachatryan commented on pull request #18963:
URL: https://github.com/apache/flink/pull/18963#issuecomment-1058451265


   I'm not sure I fully understand the question. 
   I think the state is missing for checkpoint 11, not for savepoint 12.
   From the logs, I see that the task in question has already received an 
abortion notification for checkpoint 11 (and therefore discarded it's state):
   ```
   2022-03-03 14:30:11,241 INFO  
org.apache.flink.streaming.runtime.tasks.AsyncCheckpointRunnable [] - 
ArtificalKeyedStateMapper_Kryo_and_Custom_Stateful (3/4)#0 - asynchronous part 
of checkpoint 11 could not be completed.
   java.util.concurrent.CancellationException: null
       at java.util.concurrent.FutureTask.report(FutureTask.java:121) 
~[?:1.8.0_322]
       at java.util.concurrent.FutureTask.get(FutureTask.java:192) 
~[?:1.8.0_322]
       at 
org.apache.flink.util.concurrent.FutureUtils.runIfNotDoneAndGet(FutureUtils.java:645)
 ~[flink-dist-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
       at 
org.apache.flink.streaming.api.operators.OperatorSnapshotFinalizer.<init>(OperatorSnapshotFinalizer.java:57)
 ~[flink-dist-1.15-SNAPSHOT .jar:1.15-SNAPSHOT]
       at 
org.apache.flink.streaming.runtime.tasks.AsyncCheckpointRunnable.finalizeNonFinishedSnapshots(AsyncCheckpointRunnable.java:191)
 ~[flink -dist-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
       at 
org.apache.flink.streaming.runtime.tasks.AsyncCheckpointRunnable.run(AsyncCheckpointRunnable.java:124)
 [flink-dist-1.15-SNAPSHOT.jar:1. 15-SNAPSHOT]
       at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_322]
       at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_322]
       at java.lang.Thread.run(Thread.java:750) [?:1.8.0_322]
   ```
   
   After that, it shouldn't report it to the JM however.
   It also shouldn't re-use the same file.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to