[jira] [Updated] (MAPREDUCE-7151) RMContainerAllocator#handleJobPriorityChange expects application_priority always

2018-10-24 Thread Bibin A Chundatt (JIRA) 


 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bibin A Chundatt updated MAPREDUCE-7151:

Fix Version/s: 3.1.2
   3.2.1

> RMContainerAllocator#handleJobPriorityChange expects application_priority 
> always
> 
>
> Key: MAPREDUCE-7151
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7151
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Reporter: Bibin A Chundatt
>Assignee: Bilwa S T
>Priority: Major
> Fix For: 3.1.2, 3.3.0, 3.2.1
>
> Attachments: MAPREDUCE-7151-001.patch, MAPREDUCE-7151-002.patch
>
>
> As per yarn_service.proto {{AllocateResponseProto}} *application_priority* is 
> *optional* field.
> But {{RMContainerAllocator#handleJobPriorityChange}} expects to have 
> application priority always in response which is not mandatory.
> {code}
>   private void handleJobPriorityChange(AllocateResponse response) {
> Priority priorityFromResponse = Priority.newInstance(response
> .getApplicationPriority().getPriority());
> // Update the job priority to Job directly.
> getJob().setJobPriority(priorityFromResponse);
>   }
> {code}
> {code}
> message AllocateResponseProto {
> ..
>   optional hadoop.common.TokenProto am_rm_token = 12;
>   optional PriorityProto application_priority = 13;
>   optional CollectorInfoProto collector_info = 14;
> ..
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

[jira] [Commented] (MAPREDUCE-7151) RMContainerAllocator#handleJobPriorityChange expects application_priority always

2018-10-24 Thread Hudson (JIRA) 


[ 
https://issues.apache.org/jira/browse/MAPREDUCE-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662652#comment-16662652
 ] 

Hudson commented on MAPREDUCE-7151:
---

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15309 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15309/])
MAPREDUCE-7151. RMContainerAllocator#handleJobPriorityChange expects 
(bibinchundatt: rev 74a5e683fe65ee624a094de77940a42777ed7a26)
* (edit) 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
* (edit) 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java


> RMContainerAllocator#handleJobPriorityChange expects application_priority 
> always
> 
>
> Key: MAPREDUCE-7151
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7151
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Reporter: Bibin A Chundatt
>Assignee: Bilwa S T
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: MAPREDUCE-7151-001.patch, MAPREDUCE-7151-002.patch
>
>
> As per yarn_service.proto {{AllocateResponseProto}} *application_priority* is 
> *optional* field.
> But {{RMContainerAllocator#handleJobPriorityChange}} expects to have 
> application priority always in response which is not mandatory.
> {code}
>   private void handleJobPriorityChange(AllocateResponse response) {
> Priority priorityFromResponse = Priority.newInstance(response
> .getApplicationPriority().getPriority());
> // Update the job priority to Job directly.
> getJob().setJobPriority(priorityFromResponse);
>   }
> {code}
> {code}
> message AllocateResponseProto {
> ..
>   optional hadoop.common.TokenProto am_rm_token = 12;
>   optional PriorityProto application_priority = 13;
>   optional CollectorInfoProto collector_info = 14;
> ..
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

[jira] [Updated] (MAPREDUCE-7151) RMContainerAllocator#handleJobPriorityChange expects application_priority always

2018-10-24 Thread Bibin A Chundatt (JIRA) 


 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bibin A Chundatt updated MAPREDUCE-7151:

   Resolution: Fixed
Fix Version/s: 3.3.0
   Status: Resolved  (was: Patch Available)

Committed to trunk.

> RMContainerAllocator#handleJobPriorityChange expects application_priority 
> always
> 
>
> Key: MAPREDUCE-7151
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7151
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Reporter: Bibin A Chundatt
>Assignee: Bilwa S T
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: MAPREDUCE-7151-001.patch, MAPREDUCE-7151-002.patch
>
>
> As per yarn_service.proto {{AllocateResponseProto}} *application_priority* is 
> *optional* field.
> But {{RMContainerAllocator#handleJobPriorityChange}} expects to have 
> application priority always in response which is not mandatory.
> {code}
>   private void handleJobPriorityChange(AllocateResponse response) {
> Priority priorityFromResponse = Priority.newInstance(response
> .getApplicationPriority().getPriority());
> // Update the job priority to Job directly.
> getJob().setJobPriority(priorityFromResponse);
>   }
> {code}
> {code}
> message AllocateResponseProto {
> ..
>   optional hadoop.common.TokenProto am_rm_token = 12;
>   optional PriorityProto application_priority = 13;
>   optional CollectorInfoProto collector_info = 14;
> ..
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org