[jira] [Assigned] (MAPREDUCE-6976) mapred job -set-priority claims to set priority higher than yarn.cluster.max-application-priority

2020-07-09 Thread Bilwa S T (Jira) 


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

Bilwa S T reassigned MAPREDUCE-6976:


Assignee: (was: Bilwa S T)

> mapred job -set-priority claims to set priority higher than 
> yarn.cluster.max-application-priority
> -
>
> Key: MAPREDUCE-6976
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6976
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 2.9.0, 2.8.1, 3.1.0
>Reporter: Eric Payne
>Priority: Minor
>
> With {{yarn.cluster.max-application-priority}} set to 20 and 
> {{job_1507226760578_0002}} running at priority 0, run the following command:
> {noformat}
> $ mapred job -set-priority job_1507226760578_0002 21
> Changed job priority.
> {noformat}
> The above commands sets {{job_1507226760578_0002}} to priority 20. If 
> {{job_1507226760578_0002}} is already at 20, the command does nothing.
> Compare this behavior to running the {{yarn application -updatePriority}} 
> command:
> {code}
> $ yarn application -updatePriority 21 -appId application_1507226760578_0002
> Updating priority of an aplication application_1507226760578_0002
> Updated priority of an application  application_1507226760578_0002 to cluster 
> max priority OR keeping old priority as application is in final states
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Assigned] (MAPREDUCE-6976) mapred job -set-priority claims to set priority higher than yarn.cluster.max-application-priority

2020-05-28 Thread Bilwa S T (Jira) 


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

Bilwa S T reassigned MAPREDUCE-6976:


Assignee: Bilwa S T

> mapred job -set-priority claims to set priority higher than 
> yarn.cluster.max-application-priority
> -
>
> Key: MAPREDUCE-6976
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6976
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 2.9.0, 2.8.1, 3.1.0
>Reporter: Eric Payne
>Assignee: Bilwa S T
>Priority: Minor
>
> With {{yarn.cluster.max-application-priority}} set to 20 and 
> {{job_1507226760578_0002}} running at priority 0, run the following command:
> {noformat}
> $ mapred job -set-priority job_1507226760578_0002 21
> Changed job priority.
> {noformat}
> The above commands sets {{job_1507226760578_0002}} to priority 20. If 
> {{job_1507226760578_0002}} is already at 20, the command does nothing.
> Compare this behavior to running the {{yarn application -updatePriority}} 
> command:
> {code}
> $ yarn application -updatePriority 21 -appId application_1507226760578_0002
> Updating priority of an aplication application_1507226760578_0002
> Updated priority of an application  application_1507226760578_0002 to cluster 
> max priority OR keeping old priority as application is in final states
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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