ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-2824) IGFS: File close should require only one meta transaction.
Date Tue, 22 Mar 2016 09:37:25 GMT

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

Vladimir Ozerov closed IGNITE-2824.
-----------------------------------

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

Mime
View raw message