[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745506#comment-14745506 ]
Sunil G commented on MAPREDUCE-5870: ------------------------------------ Hi [~jlowe] [~jianhe] [~eepayne] I thought of bringing up a point we discussed earlier as I have one more concern. To keep priority in JobStatus, and also to contact only AM (not RM) to get JobStatus, we had discussed on updating priority to AM from RM through heartbeat. However, other than updating JobStatus, I am not finding any other good useful reason for AM to know its own priority in RM. Do you see any more advantages for AM knowing its priority(may be other than MapReduce AM also). > Support for passing Job priority through Application Submission Context in > Mapreduce Side > ----------------------------------------------------------------------------------------- > > Key: MAPREDUCE-5870 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5870 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: client > Reporter: Sunil G > Assignee: Sunil G > Attachments: 0001-MAPREDUCE-5870.patch, 0002-MAPREDUCE-5870.patch, > 0003-MAPREDUCE-5870.patch, 0004-MAPREDUCE-5870.patch, > 0005-MAPREDUCE-5870.patch, 0006-MAPREDUCE-5870.patch, Yarn-2002.1.patch > > > Job Prioirty can be set from client side as below [Configuration and api]. > a. JobConf.getJobPriority() and > Job.setPriority(JobPriority priority) > b. We can also use configuration > "mapreduce.job.priority". > Now this Job priority can be passed in Application Submission > context from Client side. > Here we can reuse the MRJobConfig.PRIORITY configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)