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-1573) IGFS: mkdirs operations should be truly thread-safe
Date Wed, 30 Sep 2015 11:49:04 GMT

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

ASF GitHub Bot commented on IGNITE-1573:

GitHub user iveselovskiy opened a pull request:


    IGNITE-1573: mkdirs concurrency fixed.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/iveselovskiy/ignite ignite-1573

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #115
commit a1208cdef23ea4e81f78c99b84d19731d9ec4261
Author: iveselovskiy <iveselovskiy@gridgain.com>
Date:   2015-09-30T10:56:06Z

    IGNITE-1573: mkdirs concurrency fixed.


> IGFS: mkdirs operations should be truly thread-safe
> ---------------------------------------------------
>                 Key: IGNITE-1573
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1573
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Ivan Veselovsky
>            Assignee: Ivan Veselovsky
>             Fix For: ignite-1.5
> Need to lock all the existing parents and try to add the missing path in one transaction.
> If failed due to concurrent creation, retry from the beginning.

This message was sent by Atlassian JIRA

View raw message