[
https://issues.apache.org/jira/browse/YARN-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065713#comment-15065713
]
Naganarasimha G R commented on YARN-4490:
-----------------------------------------
hi [~mohdshahidkhan], Hope you are checking against the latest patch of the
YARN-3946 jira. As per it i have removed the status for recover!
bq. Not necessary. Diagnostics are not only meant to tell if app is waiting for
allocation
Well, later in the middle we modified the focus to only hold the status of the
app in accepted state (till it registers with RM ), as there might be too many
updates. And there were other debug jiras to capture information for other
states and also App /Appattempt was not having any states to provide the
information till it gets registed, hence this jira was focusing on providing
diagnostics for those parts
> RM restart the finished app shows wrong Diagnostics status
> ----------------------------------------------------------
>
> Key: YARN-4490
> URL: https://issues.apache.org/jira/browse/YARN-4490
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler, resourcemanager
> Reporter: Mohammad Shahid Khan
> Assignee: Mohammad Shahid Khan
>
> RM restart the finished app shows wrong Diagnostics status.
> Preconditions:
> RM recovery enable true.
> Steps:
> 1. run an application, wait application is finished.
> 2. Restart the RM
> 3. Check the application status is RM web UI
> Issue:
> Check the Diagnostic message: Attempt recovered after RM restart.
> Expected:
> The Diagnostic message should be available only for the application waiting
> for allocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
