[
https://issues.apache.org/jira/browse/HADOOP-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923217#comment-13923217
]
Chris Nauroth commented on HADOOP-10391:
----------------------------------------
Here is the stack trace seen since incorporating HADOOP-10211. Thank you to
[~dbalykin] and [~rramya] for reporting the bug.
{code}
2014-03-06 14:03:08,930 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode:
Exception in namenode join
java.lang.IllegalArgumentException: No enum const class
org.apache.hadoop.security.SaslRpcServer$QualityOfProtection.NONE
at java.lang.Enum.valueOf(Enum.java:196)
at
org.apache.hadoop.security.SaslRpcServer$QualityOfProtection.valueOf(SaslRpcServer.java:74)
at org.apache.hadoop.security.SaslRpcServer.init(SaslRpcServer.java:187)
at org.apache.hadoop.ipc.Server.<init>(Server.java:2156)
at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:897)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server.<init>(ProtobufRpcEngine.java:505)
at
org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:480)
at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:742)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.<init>(NameNodeRpcServer.java:296)
{code}
> HADOOP-10211 change for comma-separated list of QOP values broke
> backwards-compatibility with existing configs.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10391
> URL: https://issues.apache.org/jira/browse/HADOOP-10391
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.4.0
> Reporter: Chris Nauroth
> Priority: Blocker
>
> HADOOP-10211 changed parsing of QOP values to support a comma-separated list.
> This change accidentally broke backwards-compatibility with existing
> configs. Previously, an unrecognized value caused it to default to
> authentication. Now, an unrecognized value causes
> {{IllegalArgumentException}}. Some deployments had been using a value of
> "none" in insecure clusters, so the change would break those existing
> deployments.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
