hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.
Date Wed, 12 Oct 2016 21:59:20 GMT

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

Li Lu commented on YARN-5699:
-----------------------------

bq. Are you proposing elevating all event info items to the entity info unless they really
belong only to events?

This is my intention. If the event carries information about the timeline entity, why not
posting it as an entity level info? 

> Retrospect yarn entity fields which are publishing in events info fields.
> -------------------------------------------------------------------------
>
>                 Key: YARN-5699
>                 URL: https://issues.apache.org/jira/browse/YARN-5699
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-5699.YARN-5355.patch, 0001-YARN-5699.patch, 0002-YARN-5699.YARN-5355.patch
>
>
> Currently, all the container information are published at 2 places. Some of them are
at entity info(top-level) and some are  at event info. 
> For containers, some of the event info should be published at container info level. For
example : container exist status, container state, createdTime, finished time. These are general
information to container required for container-report. So it is better to publish at top
level info field. 



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

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


Mime
View raw message