hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4111) Killed application diagnostics message should be set rather having static mesage
Date Fri, 25 Sep 2015 15:48:04 GMT

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

Sunil G commented on YARN-4111:
-------------------------------

Yes [~rohithsharma]. This will be better.
But one thing to remember is, RMAppEvent or RMAppAttemptEvent is used in success cases also.
Hence diagnostics is not mandatory in all RMApp or RMAppAttempt events raised. 
So in places where we want to use diagnostics, it can be passed as needed (failure cases like
KILL or TIMEOUT). Existing ctor needs to retained in these events.

> Killed application diagnostics message should be set rather having static mesage
> --------------------------------------------------------------------------------
>
>                 Key: YARN-4111
>                 URL: https://issues.apache.org/jira/browse/YARN-4111
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: nijel
>         Attachments: YARN-4111_1.patch, YARN-4111_2.patch, YARN-4111_3.patch, YARN-4111_4.patch
>
>
> Application can be killed either by *user via ClientRMService* OR *from scheduler*. Currently
diagnostic message is set statically i.e {{Application killed by user.}} neverthless of application
killed by scheduler. This brings the confusion to the user after application is Killed that
he did not kill application at all but diagnostic message depicts that 'application is killed
by user'.
> It would be useful if the diagnostic message are different for each cause of KILL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message