You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/03/22 05:09:25 UTC
[jira] Commented: (HADOOP-3070) Trash not being expunged, Trash
Emptier thread gone by NPE
[ https://issues.apache.org/jira/browse/HADOOP-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581243#action_12581243 ]
Owen O'Malley commented on HADOOP-3070:
---------------------------------------
+1 for 16.2
I would also add a catch at the outer level of the run method to catch runtime exceptions.
> Trash not being expunged, Trash Emptier thread gone by NPE
> ----------------------------------------------------------
>
> Key: HADOOP-3070
> URL: https://issues.apache.org/jira/browse/HADOOP-3070
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.16.0, 0.16.1
> Reporter: Koji Noguchi
> Fix For: 0.16.2
>
> Attachments: H3070.0.16.1.patch
>
>
> We noticed that the users' trash were not being expunged by the namenode.
> jstack didn't show the Trash.Emptier thread and .out file showed
> Exception in thread "Trash Emptier" java.lang.NullPointerException
> at org.apache.hadoop.fs.Trash.expunge(Trash.java:146)
> at org.apache.hadoop.fs.Trash$Emptier.run(Trash.java:233)
> at java.lang.Thread.run(Thread.java:619)
> It seems like this happens when it hits the user's directory which doesn't contain the .Trash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.