flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Kruber (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-5908) Blob Cache can (rarely) get corrupted on failed blob downloads
Date Fri, 06 Oct 2017 09:48:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Nico Kruber closed FLINK-5908.
       Resolution: Fixed
         Assignee: Nico Kruber
    Fix Version/s: 1.4.0

This should be fixed by FLINK-7068. Please re-open if it occurs again.

> Blob Cache can (rarely) get corrupted on failed blob downloads
> --------------------------------------------------------------
>                 Key: FLINK-5908
>                 URL: https://issues.apache.org/jira/browse/FLINK-5908
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination, Network
>    Affects Versions: 1.2.0, 1.3.0, 1.4.0
>            Reporter: Stephan Ewen
>            Assignee: Nico Kruber
>             Fix For: 1.4.0
> The Blob Cache downloads files directly to the target file location.
> While it tries to clean up failed attempts, there is a change that this cleanup does
not complete.
> In that case, we have a corrupt file at the target location. The blob cache then assumes
that it already has the file cached already and future requests do not attempt to re-download
the file.
> The fix would be to download to a temp file name, validate the integrity, and rename
to the target file path when the validation succeeds.
> The validation for "content addressable" could even include validating the checksum hash.

This message was sent by Atlassian JIRA

View raw message