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

Jason Lowe commented on YARN-4141:
----------------------------------

When the user tries to verify the priority they will get an app report showing 
the job is in a terminal state which will explain why the priority isn't 
updated.  This is akin to killing an application that already completed.  We 
don't retroactively mark it as killed, and we also don't report an error to the 
user when they tried to kill the terminated application.

> Runtime Application Priority change should not throw exception for 
> applications at finishing states
> ---------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4141
>                 URL: https://issues.apache.org/jira/browse/YARN-4141
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-4141.patch, 0002-YARN-4141.patch
>
>
> As suggested by [~jlowe] in 
> [MAPREDUCE-5870-comment|https://issues.apache.org/jira/browse/MAPREDUCE-5870?focusedCommentId=14737035&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14737035]
>  , its good that if YARN can suppress exceptions during change application 
> priority calls for applications at its finishing stages.
> Currently it will be difficult for clients to handle this. This will be 
> similar to kill application behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to