hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker
Date Thu, 12 Mar 2009 13:14:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681303#action_12681303
] 

Vinod K V commented on HADOOP-5396:
-----------------------------------

As Hemanth pointed out, administrators themselves want a separate file for Queue ACLs for
better operations. Also, queue properties cannot be merged into policy file as they are completely
independent. Further, hadoop-policy.xml is applicable to all of Hadoop components whereas
ACL file is applicable only to mapred JT.

Owen also, in an offline discussion, +1'ed the proposal for a separate file with a SIGHUP
like a mechanism, also reusing mradmin refresh utility.

So, I am going with this approach, will soon upload a patch.

> Queue ACLs should be refreshed without requiring a restart of the job tracker
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-5396
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5396
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Hemanth Yamijala
>            Assignee: Vinod K V
>
> In large shared deployments of the M/R clusters, it is normal that new users will periodically
want to get access to some queues on the M/R framework. Requiring a JT restart for each such
change is operationally inconvenient and seems an overkill. There should be a way for updating
ACLs with new users without requiring a JT restart.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message