Naganarasimha G R commented on YARN-3692:

Seems like patch doesnt seem to apply on branch-2
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project hadoop-yarn-server-resourcemanager: Compilation failure: Compilation 
 local variable diagnostic is accessed from within inner class; needs to be 
declared final
 local variable diagnostic is accessed from within inner class; needs to be 
declared final

also shall i commit for 2.8?

> Allow REST API to set a user generated message when killing an application
> --------------------------------------------------------------------------
>                 Key: YARN-3692
>                 URL: https://issues.apache.org/jira/browse/YARN-3692
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Rajat Jain
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-3692.patch, 0002-YARN-3692.patch, 
> 0003-YARN-3692.patch, 0004-YARN-3692.patch, 0005-YARN-3692.1.patch, 
> 0005-YARN-3692.patch, 0006-YARN-3692.patch, 0007-YARN-3692.1.patch, 
> 0007-YARN-3692.patch
> Currently YARN's REST API supports killing an application without setting a 
> diagnostic message. It would be good to provide that support.
> *Use Case*
> Usually this helps in workflow management in a multi-tenant environment when 
> the workflow scheduler (or the hadoop admin) wants to kill a job - and let 
> the user know the reason why the job was killed. Killing the job by setting a 
> diagnostic message is a very good solution for that. Ideally, we can set the 
> diagnostic message on all such interface:
> yarn kill -applicationId ... -diagnosticMessage "some message added by 
> admin/workflow"
> REST API { 'state': 'KILLED', 'diagnosticMessage': 'some message added by 
> admin/workflow'}

This message was sent by Atlassian JIRA

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

Reply via email to