hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8879) Quota by storage type usage incorrectly initialized upon namenode restart
Date Fri, 28 Aug 2015 18:28:46 GMT

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

Kihwal Lee updated HDFS-8879:
-----------------------------
    Fix Version/s:     (was: 2.8.0)
                   2.7.2
                   3.0.0

> 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: 3.0.0, 2.7.2
>
>         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)

Mime
View raw message