[
https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461634#comment-15461634
]
Brahma Reddy Battula commented on YARN-3692:
--------------------------------------------
{{ResourceMgrDelegate.java}} in {{hadoop-mapreduce-client-jobclient}} project
and unfortunately jenkins did not run this project, hence it's missed.
bq.relaunching jenkins again.
so if relanuch also jenkins will not catch..
I think, we need to run mvn install in all projects..? [~aw] am I right..?
{noformat}
maven install: patch
============================================================================
============================================================================
cd /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch
-DskipTests -fae clean install -DskipTests=true -Dmaven.javadoc.skip=true
-Dcheckstyle.skip=true -Dfindbugs.skip=true >
/testptch/hadoop/patchprocess/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
2>&1
Elapsed: 0m 24s
cd /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch
-DskipTests -fae clean install -DskipTests=true -Dmaven.javadoc.skip=true
-Dcheckstyle.skip=true -Dfindbugs.skip=true >
/testptch/hadoop/patchprocess/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
2>&1
Elapsed: 0m 29s
cd
/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch
-DskipTests -fae clean install -DskipTests=true -Dmaven.javadoc.skip=true
-Dcheckstyle.skip=true -Dfindbugs.skip=true >
/testptch/hadoop/patchprocess/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
2>&1
Elapsed: 0m 40s
cd /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch
-DskipTests -fae clean install -DskipTests=true -Dmaven.javadoc.skip=true
-Dcheckstyle.skip=true -Dfindbugs.skip=true >
/testptch/hadoop/patchprocess/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
2>&1
Elapsed: 0m 20s
{noformat}
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
