[
https://issues.apache.org/jira/browse/HDFS-14052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774502#comment-16774502
]
CR Hota commented on HDFS-14052:
--------------------------------
[~elgoiri] [~brahmareddy] Thanks for the earlier comments.
I added a test to make sure router start up fails if the spnego principal is
not set. The test only sees IOException, we can't catch the ServletException as
it get thrown back as IOException to top of stack trace.
BTW, the build fails and seems to be caused by checkin for
[HDFS-14249|https://github.com/apache/hadoop/commit/f476bb1ee946d8d3ed1824d0858de2b1fef60b67].
Is someone looking into it? Feel free to let me know if you want me take a
look.
> RBF: Use Router keytab for WebHDFS
> ----------------------------------
>
> Key: HDFS-14052
> URL: https://issues.apache.org/jira/browse/HDFS-14052
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: CR Hota
> Priority: Major
> Attachments: HDFS-14052-HDFS-13891.0.patch,
> HDFS-14052-HDFS-13891.1.patch
>
>
> When the RouterHttpServer starts it does:
> {code}
> NameNodeHttpServer.initWebHdfs(conf, httpAddress.getHostName(),
> httpServer,
> RouterWebHdfsMethods.class.getPackage().getName());
> {code}
> This function is in the NN and is pretty generic.
> However, it then calls to NameNodeHttpServer#getAuthFilterParams, which does:
> {code}
> String httpKeytab = conf.get(DFSUtil.getSpnegoKeytabKey(conf,
> DFSConfigKeys.DFS_NAMENODE_KEYTAB_FILE_KEY));
> {code}
> In most cases, the regular web keytab will kick in, but we should make this a
> parameter and load the Router one just in case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
