[ 
https://issues.apache.org/jira/browse/HADOOP-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886033#comment-13886033
 ] 

Andrew Purtell commented on HADOOP-10310:
-----------------------------------------

Pretty sure HADOOP-8983 wasn't the breaking change

> SaslRpcServer should be initialized even when no secret manager present
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-10310
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10310
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.3.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>            Priority: Blocker
>         Attachments: HADOOP-10310.patch
>
>
> HADOOP-8983 made a change which caused the SaslRpcServer not to be 
> initialized if there is no secret manager present. This works fine for most 
> Hadoop daemons because they need a secret manager to do their business, but 
> JournalNodes do not. The result of this is that JournalNodes are broken and 
> will not handle RPCs in a Kerberos-enabled environment, since the 
> SaslRpcServer will not be initialized.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to