[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567797#comment-15567797
]
Rohith Sharma K S commented on YARN-5699:
-----------------------------------------
To me, goal for moving event info to entity info is {{User should be able to
get application/application-attempt/container reports at entity-info rather
than entity-event-info.}} The main advantage is user need not iterate trough
every events to get the report details. Iterating is time consuming when
rendering data in web UI by deserializing the pay load.
[~gtCarrera9]
bq. A bigger concern is on the code itself. Right now we have a lot of info key
name constants ending as "EVENT_INFO",
True, I do a change removing *EVENT* in all the fields in next patches.
[~sjlee0]
bq. regarding the container state that was removed in YARN-5156; perhaps we
should add it as entity info here (with COMPLETED)?
I will make a change adding container_state in next patches
bq. we’re already setting the entity created time in l.190; do we need to add
it to the entity info? I would say, we don't need this
It is only for easier accessibility rather than going through event time stamps.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
