hadoop-common-issues mailing list archives

[jira] [Commented] (HADOOP-10280) Make Schedulables return a configurable identity of user or group

Date

Thu, 20 Mar 2014 02:25:46 GMT

[ https://issues.apache.org/jira/browse/HADOOP-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941322#comment-13941322
]
Hadoop QA commented on HADOOP-10280:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12635695/HADOOP-10280.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified
test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of
javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version
1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number
of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3685//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3685//console
This message is automatically generated.
> Make Schedulables return a configurable identity of user or group
> -----------------------------------------------------------------
>
> Key: HADOOP-10280
> URL: https://issues.apache.org/jira/browse/HADOOP-10280
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Chris Li
> Assignee: Chris Li
> Attachments: HADOOP-10280.patch, HADOOP-10280.patch, HADOOP-10280.patch, HADOOP-10280.patch
>
>
> In order to intelligently schedule incoming calls, we need to know what identity it falls
under.
> We do this by defining the Schedulable interface, which has one method, getIdentity(IdentityType
idType)
> The scheduler can then query a Schedulable object for its identity, depending on what
idType is.
> For example:
> Call 1: Made by user=Alice, group=admins
> Call 2: Made by user=Bob, group=admins
> Call 3: Made by user=Carlos, group=users
> Call 4: Made by user=Alice, group=admins
> Depending on what the identity is, we would treat these requests differently. If we query
on Username, we can bucket these 4 requests into 3 sets for Alice, Bob, and Carlos. If we
query on Groupname, we can bucket these 4 requests into 2 sets for admins and users.
> In this initial version, idType can be username or primary group. In future versions,
it could be jobID, request class (read or write), or some explicit QoS field. These are user-defined,
and will be reloaded on callqueue refresh.
--
This message was sent by Atlassian JIRA
(v6.2#6252)