hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11333) Namenode unable to start if plugins can not be found
Date Sat, 14 Jan 2017 19:34:26 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822925#comment-15822925

Allen Wittenauer commented on HDFS-11333:

Plugins are used for a variety of things, including security.  Starting up the NN when a security
plugin is missing will also lower the security of the NN. That would be a *very* bad thing.
 It seems like catching, logging, and then failing to start is the correct behavior. 

> Namenode unable to start if plugins can not be found
> ----------------------------------------------------
>                 Key: HDFS-11333
>                 URL: https://issues.apache.org/jira/browse/HDFS-11333
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.21.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>              Labels: supportability
>         Attachments: HDFS-11333.001.patch
> If NameNode is unable to find plugins (specified in dfs.namenode.plugins), it terminates
abruptly with the following stack trace:
> {quote}
> Failed to start namenode.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class XXX not found
>   at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:2178)
>   at org.apache.hadoop.conf.Configuration.getInstances(Configuration.java:2250)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:713)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:691)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:843)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:822)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1543)
>   at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1611)
> {quote}
> We should catch this exception, log a warning message and let it proceed, as missing
the third party library does not affect the functionality of NameNode. We caught this bug
during a CDH upgrade where a third party plugin was not in the lib directory of the newer
version of CDH.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message