[ https://issues.apache.org/jira/browse/HDFS-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao updated HDFS-8879: ----------------------------- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Status: Resolved (was: Patch Available) Thanks all for the review. I've checked in the fix to trunk and branch-2. > Quota by storage type usage incorrectly initialized upon namenode restart > ------------------------------------------------------------------------- > > Key: HDFS-8879 > URL: https://issues.apache.org/jira/browse/HDFS-8879 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.7.0 > Reporter: Kihwal Lee > Assignee: Xiaoyu Yao > Fix For: 2.8.0 > > Attachments: HDFS-8879.01.patch > > > This was found by [~kihwal] as part of HDFS-8865 work in this > [comment|https://issues.apache.org/jira/browse/HDFS-8865?focusedCommentId=14660904&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14660904]. > The unit test > testQuotaByStorageTypePersistenceInFsImage/testQuotaByStorageTypePersistenceInFsEdit > failed to detect this because they were using an obsolete > FsDirectory instance. Once added the highlighted line below, the issue can be > reproed. > {code} > ++++>fsdir = cluster.getNamesystem().getFSDirectory(); > INode testDirNodeAfterNNRestart = fsdir.getINode4Write(testDir.toString()); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)