[
https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005942#comment-15005942
]
Steve Loughran commented on MAPREDUCE-6548:
-------------------------------------------
modifying jobclient will do nothing for any other work submitted to the YARN
scheduler: hive+Tez, spark on yarn, etc.
what about having a special queue for the critical job which can pre-empt
others' work? That way even if the cluster is full, your job wins. And their
stuff just gets blocked until there is capacity
> Jobs executed can be configurated with specific users and time hours
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-6548
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: job submission
> Affects Versions: 2.7.1
> Reporter: Lin Yiqun
> Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6548.001.patch
>
>
> In recent hadoop versions,the system has no limitation for users to execute
> their jobs if you don't configurate ACL.And I find that the ACL is only
> called in IPC, isn't operated in job submissions.And this condition can't
> satisfied with this case that I have a very important job, and I am prepared
> to execute this job in 0 to 9 o'clock.In order to let this job executed
> quickly, I am not allowed other user's job to execute in these time. So I can
> see the result in tomorrow morning.So may be we can let jobs executed with
> specific users in specific time hours.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)