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 "Lohit Vijayarenu (JIRA)" <ji...@apache.org> on 2008/06/06 23:42:44 UTC
[jira] Updated: (HADOOP-3489) NPE in SafeModeMonitor
[ https://issues.apache.org/jira/browse/HADOOP-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu updated HADOOP-3489:
-------------------------------------
Attachment: HADOOP-3489-1.patch
How about just checking if it is not null before trying canLeave?
> NPE in SafeModeMonitor
> ----------------------
>
> Key: HADOOP-3489
> URL: https://issues.apache.org/jira/browse/HADOOP-3489
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: HADOOP-3489-1.patch
>
>
> If dfsadmin issues -safemode leave command when name-node is in the extended period of safe mode the SafeModeMonitor throws the following exception:
> {code}
> Exception in thread "org.apache.hadoop.dfs.FSNamesystem$SafeModeMonitor@dc86eb" java.lang.NullPointerException
> at org.apache.hadoop.dfs.FSNamesystem$SafeModeMonitor.run(FSNamesystem.java:3914)
> at java.lang.Thread.run(Thread.java:619)
> {code}
> The problem is that when SafeModeMonitor.run() wakes up it tries to check whether it canLeave() the safe mode, but the safe mode is off already,
> and therefore the "safemode" field is null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.