flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7883) Stop fetching source before a cancel with savepoint
Date Fri, 20 Oct 2017 22:25:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213380#comment-16213380

Chesnay Schepler commented on FLINK-7883:

There is already a {{StoppableFunction}} for this exact purpose. It's just a matter of implementing
it for all sources, and introducing a dedicated savepoint&stop command (which should effectively
subsume savepoint&cancel).

> Stop fetching source before a cancel with savepoint
> ---------------------------------------------------
>                 Key: FLINK-7883
>                 URL: https://issues.apache.org/jira/browse/FLINK-7883
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API, Kafka Connector, State Backends, Checkpointing
>    Affects Versions: 1.4.0, 1.3.2
>            Reporter: Antoine Philippot
> For a cancel with savepoint command, the JobManager trigger the cancel call once the
savepoint is finished, but during the savepoint execution, kafka source continue to poll new
messages which will not be part of the savepoint and will be replayed on the next application
> A solution could be to stop fetching the source stream task before triggering the savepoint.
> I suggest to add an interface {{StoppableFetchingSourceFunction}} with a method {{stopFetching}}
that existant SourceFunction implementations could implement.
> We can add a {{stopFetchingSource}} property in 
>  {{CheckpointOptions}} class to pass the desired behaviour from {{JobManager.handleMessage(CancelJobWithSavepoint)}}
to {{SourceStreamTask.triggerCheckpoint}}

This message was sent by Atlassian JIRA

View raw message