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

Arpit Agarwal commented on HADOOP-14969:
----------------------------------------

Thanks for taking up this improvement.

For the error message at line 1496, you can have more specific text since we 
know that SASL is configured but the HTTP policy is not set to HTTPS_ONLY. 
Looks fine otherwise.

> Improve diagnostics in secure DataNode startup
> ----------------------------------------------
>
>                 Key: HADOOP-14969
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14969
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>         Attachments: HADOOP-14969.001.patch
>
>
> When DN secure mode configuration is incorrect, it throws the following 
> exception from Datanode#checkSecureConfig
> {code}
>   private static void checkSecureConfig(DNConf dnConf, Configuration conf,
>       SecureResources resources) throws RuntimeException {
>     if (!UserGroupInformation.isSecurityEnabled()) {
>       return;
>     }
> ...
>     throw new RuntimeException("Cannot start secure DataNode without " +
>       "configuring either privileged resources or SASL RPC data transfer " +
>       "protection and SSL for HTTP.  Using privileged resources in " +
>       "combination with SASL RPC data transfer protection is not supported.");
> {code}
> The DN should print more useful diagnostics as to what exactly what went 
> wrong.
> Also when starting secure DN with resources then the startup scripts should 
> launch the SecureDataNodeStarter class. If no SASL is configured and 
> SecureDataNodeStarter is not used, then we could mention that too.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to