[ 
https://issues.apache.org/jira/browse/FLINK-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephan Ewen updated FLINK-4410:
--------------------------------
    Description: 
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.

  was:Checkpoint statistics contain the duration of a checkpoint. We should 
split this time into the synchronous and asynchronous part. This will give more 
insight into the inner workings of the checkpointing mechanism and help users 
better understand what's going on.


> 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: Stephan Ewen
>            Priority: Minor
>             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)

Reply via email to