ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1515) IGFS: delete operations should be truly thread-safe
Date Mon, 08 Aug 2016 10:47:20 GMT

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

ASF GitHub Bot commented on IGNITE-1515:
----------------------------------------

Github user iveselovskiy closed the pull request at:

    https://github.com/apache/ignite/pull/105


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

Mime
View raw message