pnowojski commented on a change in pull request #14691:
URL: https://github.com/apache/flink/pull/14691#discussion_r563686026



##########
File path: docs/ops/monitoring/checkpoint_monitoring.md
##########
@@ -74,7 +74,8 @@ For subtasks there are a couple of more detailed stats 
available.
 - **Sync Duration**: The duration of the synchronous part of the checkpoint. 
This includes snapshotting state of the operators and blocks all other activity 
on the subtask (processing records, firing timers, etc).
 - **Async Duration**: The duration of the asynchronous part of the checkpoint. 
This includes time it took to write the checkpoint on to the selected 
filesystem. For unaligned checkpoints this also includes also the time the 
subtask had to wait for last of the checkpoint barriers to arrive (alignment 
duration) and the time it took to persist the in-flight data.
 - **Alignment Duration**: The time between processing the first and the last 
checkpoint barrier. For aligned checkpoints, during the alignment, the channels 
that have already received checkpoint barrier are blocked from processing more 
data.
-- **Start Delay**: The time it took for the first checkpoint barrier to reach 
this subtasks since the checkpoint barrier has been created.
+- **Start Delay**: The time it took for the first checkpoint barrier to reach 
this subtask since the checkpoint barrier has been created.
+- **Unaligned Checkpoint**: Whether the checkpoint for the subtask is 
completed as an unaligned checkpoint. An aligned checkpoint can switch to an 
unaligned checkpoint if the alignment timeouts.

Review comment:
       I guess we also need to update `checkpoint_monitoring.zh.md`? As you 
know Chinese could you do it yourself? If not, the procedure is to create a 
special JIRA ticket (described in the `docs/README.md`) for someone to pick up.




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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to