[
https://issues.apache.org/jira/browse/FLINK-23144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386104#comment-17386104
]
Till Rohrmann commented on FLINK-23144:
---------------------------------------
Quick note on using the {{RESOLVED}} vs. the {{CLOSED}} status. {{RESOLVED}}
usually means that the original reporter of the issue needs to verify whether
the issue has been correctly fixed. Then it would be {{CLOSED}}. Since you are
the reporter, I think you can directly move it into the {{CLOSED}} state
[~roman_khachatryan]. If you hover over the status, then you also get a
tool-tip.
> Add percentiles to checkpoint stats
> -----------------------------------
>
> Key: FLINK-23144
> URL: https://issues.apache.org/jira/browse/FLINK-23144
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Checkpointing, Runtime / Web Frontend
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Currently, only min/avg/max are shown, which doesn't allow to easily assess
> checkpointing times.
> Ideally, with breakdown by operator/channel state write times and sync/async
> phases (exact requirements up to implementer)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
