[
https://issues.apache.org/jira/browse/IGNITE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-3542:
---------------------------------------
Assignee: Ivan Veselovsky (was: Vladimir Ozerov)
Fix Version/s: (was: 1.9)
2.0
[~iveselovskiy], I have doubts about {{IgfsMetaManager.softDelete}} method.
Previously we invoked {{delete}} on underlying file system if integrity check
failed. Now do not do that. Is it correct?
This delegation to underlying file system in case of concurrent change looks
strange to me, not to say the least. May be we should throw an exception if
{{!pathIds.allExists() == true}}?
> 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
(v6.3.15#6346)
