[
https://issues.apache.org/jira/browse/FLINK-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15774769#comment-15774769
]
ASF GitHub Bot commented on FLINK-4410:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/3042
Hey Stephan! Thanks for spotting the typo. The numbers are already reported
but I forgot to attach the screenshot. They are only reported for each
operator/task though, because I'm not sure what would be the best way to
summarize those numbers as simply displaying the sum or maximum as the
checkpoint alignment duration, sync/async checkpoint duration does not work
well imo.

These numbers you get for all tracked checkpoints.
> Report more information about operator checkpoints
> --------------------------------------------------
>
> Key: FLINK-4410
> URL: https://issues.apache.org/jira/browse/FLINK-4410
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing, Webfrontend
> Affects Versions: 1.1.2
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Fix For: 1.2.0
>
>
> Checkpoint statistics contain the duration of a checkpoint, measured as from
> the CheckpointCoordinator's start to the point when the acknowledge message
> came.
> We should additionally expose
> - duration of the synchronous part of a checkpoint
> - duration of the asynchronous part of a checkpoint
> - number of bytes buffered during the stream alignment phase
> - duration of the stream alignment phase
> Note: In the case of using *at-least once* semantics, the latter two will
> always be zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)