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 "kanaka kumar avvaru (JIRA)" <ji...@apache.org> on 2015/04/01 14:33:53 UTC
[jira] [Commented] (HDFS-8029) NPE during disk usage calculation on
snapshot directory, after a sub folder is deleted
[ https://issues.apache.org/jira/browse/HDFS-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390484#comment-14390484 ]
kanaka kumar avvaru commented on HDFS-8029:
-------------------------------------------
[~xyao] , the steps are same as mentioned. But it seems the patch for HDFS-7824 given by you last week fixed this issue too.
So, in the latest trunk its not reproducing. The earlier version of code was having this issue.
> NPE during disk usage calculation on snapshot directory, after a sub folder is deleted
> --------------------------------------------------------------------------------------
>
> Key: HDFS-8029
> URL: https://issues.apache.org/jira/browse/HDFS-8029
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: kanaka kumar avvaru
> Assignee: kanaka kumar avvaru
>
> ContentSummary computation is causing NullPointerException on snapshot directory if some sub directory is deleted.
> Following are the steps to reproduce the issue.
>
> 1. Create a root directory "/test"
> 2. Create sub dir named as /test/sub1
> 3. Create sub dir in sub1 as /test/sub1/sub2
> 4. Create a file at /test/sub1/file1
> 5. Create a file at /test/sub1/sub2/file1
> 6. Enable shotshot on sub1 (hadoop dfsadmin -allowSnapshot test/sub1)
> 7. Create snapshot1 on /test/sub1
> 8. Delete directory /test/sub1/sub2 (recursively)
> 9. Create snapshot2 on /test/sub1
> 10. Execute du command on /test (hadoop fs -du /test/)
>
>
> Gives NullPointerException in CLI. NameNode logs the exception as
> ... java.lang.NullPointerException at org.apache.hadoop.hdfs.server.namenode.ContentSummaryComputationContext.getBlockStoragePolicySuite(ContentSummaryComputationContext.java:122) ...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)