[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S updated YARN-3692: ------------------------------------ Description: 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'} was:Currently YARN's REST API supports killing an application without setting a diagnostic message. It would be good to provide that support. > 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 > > 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 (v6.3.4#6332)