hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10310) SaslRpcServer should be initialized even when no secret manager present
Date Wed, 29 Jan 2014 23:52:08 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Aaron T. Myers updated HADOOP-10310:

    Attachment: HADOOP-10310.patch

Here's a simple patch which addresses the issue by initializing the SaslRpcServer in the case
that there is either a secret manager OR security is enabled.

I tested this patch manually and confirmed that it works as expected. Without it, I cannot
format JNs with security enabled. With the patch, the JNs can be formatted and work just fine.

> 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

View raw message