[ https://issues.apache.org/jira/browse/FLINK-21133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281581#comment-17281581 ]
Matthias commented on FLINK-21133: ---------------------------------- Findings mentioned in duplicate FLINK-21323: {quote} When looking into FLINK-21030 analyzing the stop-with-savepoint behavior we implemented different test jobs covering the old addSource and new fromSource methods for adding sources. The stop-with-savepoint consists of two phase: Create the savepoint Stop the source to trigger finalizing the job The test failing in the second phase using fromSource does not succeed. The reason for this might be that finishTask is not implemented by SourceOperatorStreamTask in contrast to SourceStreamTask which is used when calling addSource in the job definition. Hence, the job termination is never triggered. We might have missed this due to some naming error of JobMasterStopWithSavepointIT test that is not triggered by Maven due to the wrong suffix used in this case. The IT is failing right now. FLINK-21031 is covering the fix of JobMasterStopWithSavepointIT already. {quote} > FLIP-27 Source does not work with synchronous savepoint > ------------------------------------------------------- > > Key: FLINK-21133 > URL: https://issues.apache.org/jira/browse/FLINK-21133 > Project: Flink > Issue Type: Bug > Components: API / Core, Runtime / Checkpointing > Affects Versions: 1.11.3, 1.12.1 > Reporter: Kezhu Wang > Priority: Major > > I have pushed branch > [synchronous-savepoint-conflict-with-bounded-end-input-case|https://github.com/kezhuw/flink/commits/synchronous-savepoint-conflict-with-bounded-end-input-case] > in my repository. {{SavepointITCase.testStopSavepointWithFlip27Source}} > failed due to timeout. > See also FLINK-21132 and > [apache/iceberg#2033|https://github.com/apache/iceberg/issues/2033].. -- This message was sent by Atlassian Jira (v8.3.4#803005)