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/03/22 10:37:25 UTC

[jira] [Resolved] (IGNITE-2824) IGFS: File close should require only one meta transaction.

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

Vladimir Ozerov resolved IGNITE-2824.
-------------------------------------
    Resolution: Duplicate

Already handled as a part of other IGNITE-2809 children tickets.

> IGFS: File close should require only one meta transaction.
> ----------------------------------------------------------
>
>                 Key: IGNITE-2824
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2824
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.6
>
>
> *Problem*
> Have a look at {{IgfsOutputStreamImpl.onClose(boolean)}} method. It performs two sequential calls:
> 1) meta.unlock();
> 2) meta.updateParentListingAsync().
> It spans two transactions and hence two 2PC routines, leading to less than optimal performance.
> *Solution*
> Update both file and it's parent in a single transaction. 



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