[
https://issues.apache.org/jira/browse/SAMZA-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562344#comment-16562344
]
ASF GitHub Bot commented on SAMZA-1768:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/588
> Handle corrupted OFFSET file elegantly
> --------------------------------------
>
> Key: SAMZA-1768
> URL: https://issues.apache.org/jira/browse/SAMZA-1768
> Project: Samza
> Issue Type: Bug
> Reporter: Xinyu Liu
> Assignee: Xinyu Liu
> Priority: Major
>
> TaskStorageManager.readOffsetFile() has a bug that if the OFFSET file is
> corrupted, it will throw exception and shut down the container. If host
> affinity is turned on, the container won't be able start up again since it
> will read the same corrupted OFFSET file every time, until it was manually
> removed. Since we cannot recover in this case, we should catch the exception
> and return null and let the store bootstrap from changelog.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
