You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "chaosju (Jira)" <ji...@apache.org> on 2021/11/08 07:44:00 UTC
[jira] [Updated] (YARN-3692) Allow REST API to set a user generated
message when killing an application
[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chaosju 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', 'diagnostics': '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.
*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'}
> 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
> Priority: Major
> Fix For: 2.8.0, 3.0.0-alpha2
>
> 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', 'diagnostics': 'some message added by admin/workflow'}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org