[
https://issues.apache.org/jira/browse/FLINK-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8467:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Runtime / Checkpointing
> Reporter: Jelmer Kuperus
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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]
>
> If this is not something you want to address at least the upgrading guide
> ([https://ci.apache.org/projects/flink/flink-docs-release-1.4/ops/upgrading.html)]
> should caution against this
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
