Varun Saxena commented on YARN-5743:

bq. Diagnostic report is for per node basis. This will over spam the 
application storage. 
That's true. Agree with you.

bq. aggregated log will be deleted after some time as per configuration 
configured. Since we are storing very long history of applications, very old 
applications logs might be deleted which gives wrong information to reader.
I do not think it will give wrong information to reader because its just saying 
whether log aggregation had succeeded or failed. Deletion of aggregated logs is 
a separate functionality which admins would be knowing about. 
I just thought about this because for some applications which may have failed 
in last 3-4 days, we may look for their logs and if some logs were missing, log 
aggregation status and diagnostics info may have been useful. But without 
diagnostic info, we may not get much info on what went wrong anyways. Also, log 
aggregation status will not be immediately available i.e. when finished event 
is published. So even if we do publish it, we can probably handle it in a 
different JIRA.
[~sjlee0], your thoughts on this ?

> [Atsv2] Publish queue name and RMAppMetrics to ATS
> --------------------------------------------------
>                 Key: YARN-5743
>                 URL: https://issues.apache.org/jira/browse/YARN-5743
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-5743.patch, 0002-YARN-5743.patch
> App queue name is missed to publish to ATSv2. 
> And RMAppMetrcs publish only cpu and memory. There are many more things to 
> publish from app metrics such as 
>  resourcePreempted;
>  numNonAMContainersPreempted;
> numAMContainersPreempted.
> And RMAppMetrics need to be published to App metrics rather than info. 

This message was sent by Atlassian JIRA

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

Reply via email to