You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2016/03/26 01:19:25 UTC
[jira] [Updated] (SAMZA-905) Host Affinity - State restore doesn't
work if the previous shutdown was uncontrolled (continuous offset)
[ https://issues.apache.org/jira/browse/SAMZA-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Navina Ramesh updated SAMZA-905:
--------------------------------
Summary: Host Affinity - State restore doesn't work if the previous shutdown was uncontrolled (continuous offset) (was: Host Affinity - State restore doesn't work if the previous shutdown was uncontrolled)
> Host Affinity - State restore doesn't work if the previous shutdown was uncontrolled (continuous offset)
> --------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-905
> URL: https://issues.apache.org/jira/browse/SAMZA-905
> Project: Samza
> Issue Type: Bug
> Reporter: Jake Maes
> Assignee: Jake Maes
> Fix For: 0.10.1
>
> Attachments: SAMZA-905.patch, SAMZA-905_2.patch, SAMZA-905_3.patch
>
>
> The host affinity feature writes an OFFSET file during shutdown which records the changelog offset for the persisted state store. Because the file is written at shutdown, it depends on a clean shutdown. Otherwise the file will not be there when the task restarts and the state will not be restored.
> This ticket is to add a continuous checkpointing feature so the OFFSET file is written at regular intervals and the most recent update can be used to restore state.
> Note: this feature assumes all changelog entries are idempotent as warned in https://issues.apache.org/jira/secure/attachment/12696372/DESIGN-SAMZA-516-2.pdf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)