[
https://issues.apache.org/jira/browse/HADOOP-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697015#action_12697015
]
Hemanth Yamijala commented on HADOOP-5485:
------------------------------------------
The changes look fine. One minor nit is that a new configuration object is
being created here, which i think is unnecessary. I have two solutions:
- We can use the conf object via the JSPUtil class - we could even have a
arePrivateActionsAllowed kind of method maybe.. or just a simple accessor for
the conf
- The other option is to read this particular value, cache it and discard the
conf.
> Authorisation machanism required for acceesing jobtracker url :-
> jobtracker.com:port/scheduler
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-5485
> URL: https://issues.apache.org/jira/browse/HADOOP-5485
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fair-share
> Affects Versions: 0.20.0
> Reporter: Aroop Maliakkal
> Assignee: Vinod K V
> Attachments: HADOOP-5485.txt
>
>
> FS scheduler should have some mechanism to authorize people who can access
> the advanced scheduler url http://jobtracker.com:port/scheduler . In large
> clusters , which has hundreds of users, any user can access the url now and
> change the priority of his/her runing job. We don't want the users to change
> the job priority. So we should restrcit users accessing the link and only
> admins should have access to the link.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
