[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13266491#comment-13266491 ] xieguiming commented on MAPREDUCE-4124: --- By the Yarn design goal, the AM can support multiple jobs. If like this, the priority also need pass to the AM. Job Priority is not changing - Key: MAPREDUCE-4124 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 3.0.0 Reporter: Nishan Shetty Priority: Critical 1.Submit job 2.Change the job priority using setPriority() or CLI command ./mapred job-set-priority job-id priority Observe that Job priority is not changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261930#comment-13261930 ] Robert Joseph Evans commented on MAPREDUCE-4124: I am fine with making sure that the priority information is passed up to the scheduler, and if you want to update the FIFO scheduler to go off of priority as well I don't see much of an issue with that either. But for any other scheduler I would like to see that work done as a separate JIRA because it is likely to be a lot of work, and may be somewhat controversial. Job Priority is not changing - Key: MAPREDUCE-4124 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 3.0.0 Reporter: Nishan Shetty Priority: Critical 1.Submit job 2.Change the job priority using setPriority() or CLI command ./mapred job-set-priority job-id priority Observe that Job priority is not changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[
https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260408#comment-13260408
]
xieguiming commented on MAPREDUCE-4124:
---
1, When jobclient create the ApplicationSubmissionContext, set the priority to
the ApplicationSubmissionContext.
{color:red}
Priority pri = Records.newRecord(Priority.class); // Job Priority.
pri.setPriority(jobConf.getInt(JobContext.PRIORITY,
YarnConfiguration.DEFAULT_PRIORITY));
appContext.setPriority(pri);
{color}
appContext.setAMContainerSpec(amContainer); // AM Container
2, Add one interface function in the ClientRMProtocol. and implement the
function:
public void setJobPriority(JobID arg0, String arg1) throws IOException,
InterruptedException {
{color:red}
// call the ClientRMProtocol.setApplicationPriority()
{color}
return;
}
Job Priority is not changing
-
Key: MAPREDUCE-4124
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 3.0.0
Reporter: Nishan Shetty
Priority: Critical
1.Submit job
2.Change the job priority using setPriority() or CLI command ./mapred
job-set-priority job-id priority
Observe that Job priority is not changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260589#comment-13260589 ] Robert Joseph Evans commented on MAPREDUCE-4124: I thought that the problem was deeper then that. I do not believe that any of the schedulers actually use the priority currently, so even just getting the priority over to the RM will not really do anything yet, at least not until the schedulers are updated to use priority. Job Priority is not changing - Key: MAPREDUCE-4124 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 3.0.0 Reporter: Nishan Shetty Priority: Critical 1.Submit job 2.Change the job priority using setPriority() or CLI command ./mapred job-set-priority job-id priority Observe that Job priority is not changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261290#comment-13261290 ] xieguiming commented on MAPREDUCE-4124: --- Robert, you are right. the schedulers do not use the priority currently. I think we can change the FIFOschedulers to support the priority firstly. Currently, the FIFOschedulers only sort by submiting time. and we can change to sort by priority firstly, and then by submiting time. Job Priority is not changing - Key: MAPREDUCE-4124 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 3.0.0 Reporter: Nishan Shetty Priority: Critical 1.Submit job 2.Change the job priority using setPriority() or CLI command ./mapred job-set-priority job-id priority Observe that Job priority is not changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
