hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4777) File creation code in namenode is incorrectly synchronized
Date Mon, 29 Apr 2013 23:20:15 GMT

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

Suresh Srinivas commented on HDFS-4777:
---------------------------------------

FSNamesystem calls delete:
{code}
        // File exists - must be one of append or overwrite
        if (overwrite) {
          delete(src, true);
        } else {
{code}

and {{deleteInternal()}} release the lock.
                
> File creation code in namenode is incorrectly synchronized
> ----------------------------------------------------------
>
>                 Key: HDFS-4777
>                 URL: https://issues.apache.org/jira/browse/HDFS-4777
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.23.0, 2.0.0-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>
> FSNamesystem#startFileInternal calls delete. Delete method releases the write lock, making
parts of startFileInternal code unintentionally executed without write lock being held.

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

Mime
View raw message