hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application
Date Tue, 30 Aug 2016 09:49:21 GMT

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

Hadoop QA commented on YARN-3692:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 9s {color} | {color:red}
YARN-3692 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12798487/0001-YARN-3692.patch
|
| JIRA Issue | YARN-3692 |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/12939/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>
>
> 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)

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


Mime
View raw message