[
https://issues.apache.org/jira/browse/HDFS-14390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819252#comment-16819252
]
Daryn Sharp commented on HDFS-14390:
------------------------------------
Ok, so the kerberos annotation is effectively the only change. You should make
a call via the fs instance, ex. getServerDefaults, to ensure that it can
actually connect and authenticate. The mini-cluster has probably already used
the fs but I wouldn't rely on it.
I don't think the {{FSTreeWalk}} change is a good idea. Is it actually needed?
The login user is the current user unless an explicit doAs another identity
has been done in which it was probably done for good reason. Why add a latent
surprise that second-guesses the caller and reverts back to the login user?
> Provide kerberos support for AliasMap service used by Provided storage
> ----------------------------------------------------------------------
>
> Key: HDFS-14390
> URL: https://issues.apache.org/jira/browse/HDFS-14390
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ashvin
> Assignee: Ashvin
> Priority: Major
> Attachments: HDFS-14390.001.patch, HDFS-14390.002.patch,
> HDFS-14390.003.patch, HDFS-14390.004.patch
>
>
> With {{PROVIDED}} storage (-HDFS-9806)-, HDFS can address data stored in
> external storage systems. This feature is not supported in a secure HDFS
> cluster. The {{AliasMap}} service does not support kerberos, and as a result
> the cluster nodes will fail to communicate with it. This JIRA is to enable
> kerberos support for the {{AliasMap}} service.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
