[ https://issues.apache.org/jira/browse/FLINK-20488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256293#comment-17256293 ]
Yuan Mei commented on FLINK-20488: ---------------------------------- A bit more details: On the high-level, people want to understand whether the checkpoint is completed as an aligned or unaligned checkpoint; so at least we should have types of checkpoints completed as {{ALIGNED_CHECKPOINT}} or {{UN_ALIGNED_CHECKPOINT}} {{}} {{}}For each type, there are separate cases: {{}} {{ALIGNED_CHECKPOINT}} : *case1:* aligned with no timeout (unaligned checkpoint is disabled); *case2:* aligned without being timed out (unaligned checkpoint is enabled, but alignment duration < timeout) {{UN_ALIGNED_CHECKPOINT}} : *case3:* unaligned with no timeout (unaligned is enabled, but not allowed to be switched back to aligned *case4:* unaligned due to being timed out (unaligned checkpoint is enabled, alignment duration > timeout) *case 5:* we have an additional case where we are NOT in {{ExactlyOnceMode}} > Show checkpoint type in the UI (AC/UC) for each subtask > ------------------------------------------------------- > > Key: FLINK-20488 > URL: https://issues.apache.org/jira/browse/FLINK-20488 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing, Runtime / Configuration, > Runtime / Web Frontend > Affects Versions: 1.12.0 > Reporter: Roman Khachatryan > Priority: Major > > A follow-up ticket after FLINK-19681 to address issues not directly related > to checkpointing (see > [discussion|https://github.com/apache/flink/pull/13827#discussion_r527794600]). > > In the UI, show checkpoint type for each subtask; on a checkpoint level > display unaligned if at least one subtask did UC. > That should ease debugging of the checkpointing issues. > > Disabling propagation moved to FLINK-20548. -- This message was sent by Atlassian Jira (v8.3.4#803005)