You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/01/04 02:48:12 UTC

[jira] [Updated] (HDFS-4357) After calling replaceSelf, further operations that should be applied on the new INode may be wrongly applied to the original INode

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

Jing Zhao updated HDFS-4357:
----------------------------

    Summary: After calling replaceSelf, further operations that should be applied on the new INode may be wrongly applied to the original INode  (was: After calling replaceSelf, further operations that should be processed on the new INode may be applied to the original INode)
    
> After calling replaceSelf, further operations that should be applied on the new INode may be wrongly applied to the original INode
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4357
>                 URL: https://issues.apache.org/jira/browse/HDFS-4357
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>
> An example is in INode#setModificationTime, if the INode is an instance of INodeDirectory, after replacing itself with a new INodeDirectoryWithSnapshot, the change of the modification time should happen in the new INodeDirectoryWithSnapshot instead of the original INodeDirectory.

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