ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Veselovsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.
Date Fri, 10 Mar 2017 15:05:04 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905208#comment-15905208

Ivan Veselovsky commented on IGNITE-3542:

[~vozerov] , 
1) The suggested fix does not prevent the {code}delete{code} to be invoked on underlying Fs
in case integrity check failed, we just do retry and go to next loop in this case. This is
exactly what is requested by this ticket.
2)  Agree, I'm not sure what to do best in case {code}!pathIds.allExists(){code} -- deletion
on secondary Fs really looks strange, but that is an existing functionality. But I guess 
 we should not throw an Exception in this case, but rather should return {code}new IgfsDeleteResult(false,
null);{code}, shouldn't we? 

> IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.
> -----------------------------------------------------------------
>                 Key: IGNITE-3542
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3542
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Ivan Veselovsky
>            Priority: Minor
>             Fix For: 2.0
> If integrity check failed, it means that some concurrent file system update occurred.
We should always perform re-try in this case.

This message was sent by Atlassian JIRA

View raw message