hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6294) Use INode IDs to avoid conflicts when a file open for write is renamed
Date Tue, 29 Apr 2014 06:15:17 GMT

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

Vinayakumar B commented on HDFS-6294:
-------------------------------------

Do you mean we can support continue writing to files even though are renamed while writing?
Is it a valid/intended behavior?

> Use INode IDs to avoid conflicts when a file open for write is renamed
> ----------------------------------------------------------------------
>
>                 Key: HDFS-6294
>                 URL: https://issues.apache.org/jira/browse/HDFS-6294
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.20.1
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-6294.001.patch
>
>
> Now that we have a unique INode ID for each INode, clients with files that are open for
write can use this unique ID rather than a file path when they are requesting more blocks
or closing the open file.  This will avoid conflicts when a file which is open for write is
renamed, and another file with that name is created.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message