[
https://issues.apache.org/jira/browse/YARN-8895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662914#comment-16662914
]
Wangda Tan commented on YARN-8895:
----------------------------------
[~youchen] , Thanks, I believe this will be a very useful Jira. My questions:
1) How to make it compatible. Typically we don't think changing "diagnostic"
field is an incompatible change, however if everything changed, I would prefer
to have a new field.
2) What changes required to produce proposed structured msg.
> Improve YARN Error diagnostics
> -------------------------------
>
> Key: YARN-8895
> URL: https://issues.apache.org/jira/browse/YARN-8895
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Young Chen
> Assignee: Young Chen
> Priority: Minor
>
> Currently identifying error sources can be quite difficult, as they are
> written into an unstructured string "diagnostics" field. This is present in
> container statuses returned to the RM and in application attempts in the RM.
> These errors are difficult to classify without hard-coding diagnostic string
> searches.
> This Jira aims to add a structured error field in NM and RM that preserves
> failure information and source component to enable faster and clearer error
> diagnosis
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
