hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Lamb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6294) Use INode IDs to avoid conflicts when a file open for write is renamed
Date Wed, 07 May 2014 00:50:19 GMT

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

Charles Lamb commented on HDFS-6294:

NameNodeRpcServer.java: it looks like you can get rid of the // TODO comment.


      Assert.assertEquals(contents1,  DFSTestUtil.readFile(fs3, path2));
      Assert.assertEquals(contents2,  DFSTestUtil.readFile(fs3, path1));
There are two spaces after the comma in contentsN,
In the same file, I assume the out.close that you're adding was a random missing close() that
you happened upon?

TestSetrep(Inc/Dec)reasing.java: are the timeouts you are adding related to the rest of the
changes or just opportunistic/necessary?

> 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, HDFS-6294.002.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

View raw message