You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/06/28 08:54:57 UTC

[jira] [Updated] (IGNITE-1515) IGFS: delete operations should be truly thread-safe

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

Vladimir Ozerov updated IGNITE-1515:
------------------------------------
    Component/s: IGFS

> IGFS: delete operations should be truly thread-safe
> ---------------------------------------------------
>
>                 Key: IGNITE-1515
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1515
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: ignite-1.4
>            Reporter: Ivan Veselovsky
>            Assignee: Vladimir Ozerov
>             Fix For: 1.5.0.final
>
>
> In IGNITE-586 we fixed concurrency problem in rename/move operations.
> Since delete is actually also remove, we should fix deletion operations also accordingly using similar logic. 
> IgfsMetaManager#move0(2) method is to be used partially in delete operation -- need to refactor code accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)