[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Wysakowicz updated FLINK-17741: - Fix Version/s: (was: 1.13.0) 1.14.0 > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.14.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Knauf updated FLINK-17741: - Labels: (was: stale-major) Removed "stale-critical|major|minor" label in line with https://issues.apache.org/jira/browse/FLINK-22429. > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.13.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-17741: --- Labels: stale-major (was: ) > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Labels: stale-major > Fix For: 1.13.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-17741: --- Fix Version/s: (was: 1.12.0) 1.13.0 > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.13.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-17741: - Parent: FLINK-19442 Issue Type: Sub-task (was: Task) > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.12.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-17741: - Parent: (was: FLINK-14551) Issue Type: Task (was: Sub-task) > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.12.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Nowojski updated FLINK-17741: --- Fix Version/s: 1.11.0 > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.11.0 > > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17741) Create integration or e2e test for out of order (savepoint) barriers
[ https://issues.apache.org/jira/browse/FLINK-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Nowojski updated FLINK-17741: --- Parent: FLINK-14551 Issue Type: Sub-task (was: Test) > Create integration or e2e test for out of order (savepoint) barriers > > > Key: FLINK-17741 > URL: https://issues.apache.org/jira/browse/FLINK-17741 > Project: Flink > Issue Type: Sub-task > Components: Tests >Reporter: Roman Khachatryan >Priority: Major > > Unaligned checkpoints MVP assumes at most one barrier at a time. This is > ensured by max-concurrent-checkpoints on CheckpointCoordinator. > But it seems possible that CheckpointCoordinator considers a checkpoint > canceled, starts a new one, while some old barriers are still flowing in the > graph. > As of now, this situation isn't tested. -- This message was sent by Atlassian Jira (v8.3.4#803005)
