[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545289#comment-13545289
]
shenhong commented on YARN-319:
-------------------------------
The reason is at FairScheduler#addApplication, if user cannot submit job to the
queue, it return directly, we
should create a RMAppAttemptRejectedEvent and handle.
original:
// Enforce ACLs
UserGroupInformation userUgi = UserGroupInformation.createRemoteUser(user);
if (!queue.hasAccess(QueueACL.SUBMIT_APPLICATIONS, userUgi)) {
LOG.info("User " + userUgi.getUserName() +
" cannot submit applications to queue " + queue.getName());
return;
}
after modification:
// Enforce ACLs
UserGroupInformation userUgi = UserGroupInformation.createRemoteUser(user);
if (!queue.hasAccess(QueueACL.SUBMIT_APPLICATIONS, userUgi)) {
String msg = "User " + userUgi.getUserName() +
" cannot submit applications to queue " + queue.getName();
LOG.info(msg);
rmContext.getDispatcher().getEventHandler().handle(
new RMAppAttemptRejectedEvent(applicationAttemptId, msg));
return;
}
I will create a patch to fix it.
> Submit a job to a queue that not allowed in fairScheduler, client will hold
> forever.
> ------------------------------------------------------------------------------------
>
> Key: YARN-319
> URL: https://issues.apache.org/jira/browse/YARN-319
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, scheduler
> Affects Versions: 2.0.2-alpha
> Reporter: shenhong
> Fix For: 2.0.3-alpha
>
>
> RM use fairScheduler, when client submit a job to a queue, but the queue do
> not allow the user to submit job it, in this case, client will hold forever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
