[jira] [Updated] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side
[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated MAPREDUCE-5870: --- Attachment: 0002-MAPREDUCE-5870.patch Thank you [~jianhe] for the clarification. Uploading a patch based on same. 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, 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)
[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side
[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641903#comment-14641903
]
Hadoop QA commented on MAPREDUCE-5870:
--
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 16m 39s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:green}+1{color} | javac | 7m 42s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 44s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 23s | The applied patch does
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle | 0m 55s | The applied patch generated
11 new checkstyle issues (total was 33, now 44). |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 24s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 2m 0s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | mapreduce tests | 0m 47s | Tests passed in
hadoop-mapreduce-client-common. |
| {color:green}+1{color} | mapreduce tests | 110m 36s | Tests passed in
hadoop-mapreduce-client-jobclient. |
| | | 150m 54s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12747222/0002-MAPREDUCE-5870.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 156f24e |
| checkstyle |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5912/artifact/patchprocess/diffcheckstylehadoop-mapreduce-client-common.txt
|
| hadoop-mapreduce-client-common test log |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5912/artifact/patchprocess/testrun_hadoop-mapreduce-client-common.txt
|
| hadoop-mapreduce-client-jobclient test log |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5912/artifact/patchprocess/testrun_hadoop-mapreduce-client-jobclient.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5912/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf905.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5912/console |
This message was automatically generated.
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,
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)
[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side
[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642080#comment-14642080
]
Jian He commented on MAPREDUCE-5870:
[~sunilg], thanks for updating,
- should we use the JobConf.getJobPriority API so that it can accept the
current CLI specified priority too ?
{code}
String jobPriority = jobConf.get(MRJobConfig.PRIORITY);
{code}
- to simplify a little bit,
{code}
int iPriority = TypeConverter.toYarn(jobPriority);
// If the given input not a JobPriority enum, verify whether its an
// integer.
if (0 == iPriority) {
iPriority = Integer.parseInt(jobPriority);
}
{code}
we can do something like
{code}
try {
iPriority = TypeConverter.toYarn(jobPriority);
} catch (IllegalArgumentException exception) {
iPriority = Integer.parseInt(jobPriority);
}
{code}
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,
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)
[jira] [Commented] (MAPREDUCE-6394) Speed up Task processing loop in HsTasksBlock#render()
[ https://issues.apache.org/jira/browse/MAPREDUCE-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642238#comment-14642238 ] Ray Chiang commented on MAPREDUCE-6394: --- RE: checkstyle Matches surrounding method definitions. Speed up Task processing loop in HsTasksBlock#render() -- Key: MAPREDUCE-6394 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6394 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: jobhistoryserver Affects Versions: 2.7.0 Reporter: Ray Chiang Assignee: Ray Chiang Labels: supportability Attachments: MAPREDUCE-6394.001.patch, MAPREDUCE-6394.002.patch, MAPREDUCE-6394.003.patch, MAPREDUCE-6394.004.patch, MAPREDUCE-6394.005.patch, MAPREDUCE-6394.006.patch, MAPREDUCE-6394.007.patch In HsTasksBlock#render(), there is a loop to create a Javascript table which slows down immensely on jobs with a large number of tasks (200k or more). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
