Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 4 Oct 2012 09:13:08 +1100 (NCT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1590610124.162063.1349302388297.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <144149442.22456.1321049331559.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2551) fuse-dfs's close() is asynchronous
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-2551:
-----------------------------------

ah, I see. Then this seems like it might be a reasonable workaround. There's no way to do our own reference counting? (ie we don't have any clue when an fd gets duped?)
                
> fuse-dfs's close() is asynchronous
> ----------------------------------
>
>                 Key: HDFS-2551
>                 URL: https://issues.apache.org/jira/browse/HDFS-2551
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: fuse-dfs
>    Affects Versions: 0.20.205.0, 0.23.0
>            Reporter: Todd Lipcon
>
> FUSE's "release" operation is called asynchronously when a file is closed from userspace. This means that, if a program writes a file, closes it, and immediately re-opens it, it might not succeed. We should figure out some workaround or trick to make close synchronous, if possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira