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

Thomas Graves commented on MAPREDUCE-3021:
------------------------------------------

Manual testing done since no unit test framework for the links.  

Tested all the yarn webapp: resource manager, node manager, job history, and 
app master ui.  For each verified that all the links in the tables and in the 
menus properly worked and went to the new uri which would be:

resource maanger: host:port/cluster
node manager: host:port/node
job history: host:port/jobhistory 
app master: host:port/mapreduce

Note that with MAPREDUCE-2999 host:port/ gets redirected now to 
host:port/<component>.  I tested with auth filtering on 
(hadoop.http.filter.initializers) with an auth filter that allowed you to 
bypass authentication on pages as configured.  Tested this with the new naming 
conventions and verified that the pages could be bypassed with the new names 
without collision between components.

resource manager has links:
  - nodes page has links to node manager. 
  - links to containers logs on node manager for the application
  - link to job history for finished apps
  - link to app master for running apps

app master page has menu in upper left corner back to the resource manager.
app master has link to container logs on node manager

Verify all the links within a component still work.
                
> all yarn webapps use same base name of "yarn/"
> ----------------------------------------------
>
>                 Key: MAPREDUCE-3021
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3021
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3021.patch, MAPREDUCE-3021.patch
>
>
> All of the yarn webapps (resource manager, node manager, app master, job 
> history) use the same base url of /yarn/.  This doesn't lend itself very well 
> to filters be able to differentiate them to say allow some to be not 
> authenticated and other to be authenticated.  Perhaps we should rename them 
> based on component.
> There are also things in the code that hardcode paths to "/yarn" that should 
> be fixed up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to