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

CR Hota commented on HDFS-14006:
--------------------------------

[~elgoiri]  [~brahmareddy]

For this refactoring, after the analysis I could do, it may be good to just 
leave current namenode code as is. JspHelper is a class that was designed to be 
a static method holder and not really designed to be extensible. Rather than 
changing JspHelper and all its dependencies and also UserProvider(depends on 
JspHelper methods), its better to introduce RouterJspHelper and 
RouterUserProvider. There will be some duplicate code, but since this area 
doesn't change often and matured, it seems to be like a good idea to just leave 
current code as is.

In short this ticket can be marked "Workaround". At sometime in the future, 
once Router security is stabilized, we can open a new ticket to holistically 
look at how this area can be redesigned for both namenode and router 
collectively.

 

 

> RBF: Support to get Router object from web context instead of Namenode
> ----------------------------------------------------------------------
>
>                 Key: HDFS-14006
>                 URL: https://issues.apache.org/jira/browse/HDFS-14006
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: CR Hota
>            Assignee: CR Hota
>            Priority: Major
>
> Router currently uses Namenode web resources to read and verify delegation 
> tokens. This model doesn't work when router will be deployed in secured mode. 
> This change will introduce router's own UserProvider resource and 
> dependencies.
> In the current deployment one can see this exception.
> {"RemoteException":\{"exception":"ClassCastException","javaClassName":"java.lang.ClassCastException","message":"org.apache.hadoop.hdfs.server.federation.router.Router
>  cannot be cast to org.apache.hadoop.hdfs.server.namenode.NameNode"}}
> In the proposed change, router will maintain its own web resource, that will 
> be similar to current namenode, but modified to get back a router instance 
> instead of namenode.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to