1996fanrui opened a new pull request, #28972:
URL: https://github.com/apache/flink/pull/28972

   ## What is the purpose of the change
   
   Channel state recovery is silent today: a TaskManager log does not tell 
whether checkpointing
   during recovery is enabled, which recovery path a task actually took, or how 
far it got.
   This adds the missing INFO/DEBUG logs on both paths, as requested in the 
review of FLINK-40080:
   https://github.com/apache/flink/pull/28662#pullrequestreview-4921785962
   
   ## Brief change log
   
   Both paths now log an opening statement (which path, how many input gates) 
and a closing one:
   
   - Checkpointing during recovery enabled: feature enabled (INFO), 
fetch/filter result — number of
     spill files or nothing to recover (INFO), drainer installed as the 
recovery checkpoint trigger
     (DEBUG), drain start (DEBUG) and drain duration (INFO), recovery finished 
(INFO)
   - Checkpointing during recovery disabled: feature disabled (INFO) and the 
duration of feeding the
     recovered state into the input channels (INFO)
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
   


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