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 "Sunil G (Jira)" <ji...@apache.org> on 2020/06/12 15:59:00 UTC
[jira] [Assigned] (YARN-10166) Add detail log for
ApplicationAttemptNotFoundException
[ https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G reassigned YARN-10166:
------------------------------
Assignee: Youquan Lin
> Add detail log for ApplicationAttemptNotFoundException
> ------------------------------------------------------
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Reporter: Youquan Lin
> Assignee: Youquan Lin
> Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch, YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call unregisterAttempt() for this app. Sometimes, app's AM continues to call the alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_000001 doesn't exist in ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the attempt is no longer in the ApplicationMasterService cache. So I think we can add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_000001 doesn't exist in ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED ,diagnostics: App application_1582630210671_14658 killed by userA from 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org