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] [Comment Edited] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.
Date Tue, 28 Mar 2017 16:40:41 GMT

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

Ivan Veselovsky edited comment on IGNITE-3542 at 3/28/17 4:40 PM:
------------------------------------------------------------------

[~vozerov] , thanks, that was a mistake, and now it is fixed.

Note, that several tests fail on Windows agents (agent name `*_9090`), but this happens for
reasons not related to this fix (some problem with OS-locked files on rename/move, also happens
on `master` branch). Ticket IGNITE-4623 intended to fix that.


was (Author: iveselovskiy):
[~vozerov] , thanks, that was a mistake, and now it is fixed.

> 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)

Mime
View raw message