You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jelmer Kuperus (JIRA)" <ji...@apache.org> on 2018/01/20 13:36:02 UTC
[jira] [Updated] (FLINK-8467) Restoring job that does not use
checkpointing from savepoint breaks
[ https://issues.apache.org/jira/browse/FLINK-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jelmer Kuperus updated FLINK-8467:
----------------------------------
Description:
When checkpointing is disabled, the Flink Kafka Consumer relies on the periodic offsets that are committed to the broker by the internal Kafka client. Such a job would, upon restart, continue from the committed offsets. However, in the situation that the job is restored from a savepoint, then the offsets within the savepoint supercede the broker-based offsets.
Here's a simple project that demonstrates the problem : [https://github.com/jelmerk/flink-cancel-restart-job-without-checkpointing]
And a link to the mailing list thread : [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Starting-a-job-that-does-not-use-checkpointing-from-a-savepoint-is-broken-td17874.html]
was:
When checkpointing is disabled, the Flink Kafka Consumer relies on the periodic offsets that are committed to the broker by the internal Kafka client. Such a job would, upon restart, continue from the committed offsets. However, in the situation that the job is restored from a savepoint, then the offsets within the savepoint supercede the broker-based offsets.
Here's a simple project that demonstrates the problem : [https://github.com/jelmerk/flink-cancel-restart-job-without-checkpointing]
And a link to the mailing list thread : http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Starting-a-job-that-does-not-use-checkpointing-from-a-savepoint-is-broken-td17874.html
> Restoring job that does not use checkpointing from savepoint breaks
> -------------------------------------------------------------------
>
> Key: FLINK-8467
> URL: https://issues.apache.org/jira/browse/FLINK-8467
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Reporter: Jelmer Kuperus
> Priority: Major
>
> When checkpointing is disabled, the Flink Kafka Consumer relies on the periodic offsets that are committed to the broker by the internal Kafka client. Such a job would, upon restart, continue from the committed offsets. However, in the situation that the job is restored from a savepoint, then the offsets within the savepoint supercede the broker-based offsets.
> Here's a simple project that demonstrates the problem : [https://github.com/jelmerk/flink-cancel-restart-job-without-checkpointing]
> And a link to the mailing list thread : [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Starting-a-job-that-does-not-use-checkpointing-from-a-savepoint-is-broken-td17874.html]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)