[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548904#comment-15548904
]
Naganarasimha G R commented on YARN-5699:
-----------------------------------------
Thanks [~rohithsharma] & [~gtCarrera9] for detailing it out.
bq. For example : container exist status, container state, createdTime,
finished time.
Pushing these kind of information *both the places* would be fine but IMO
diagnostics kind of stuff need not be stored. Both the places to ensure
existing clients need not be impacted.
bq. Thirdly, event RM_CONTAINER_CREATED holds diagnostics, state and status.
IIUC you mean container finished right ?
In between (not related to this jira ) One more thing i was noticing was how
will user know what are the different entity types present which needs to be
queried, do we need to capture in our documentation ? For example MR entities,
what are the different entity ID's to query ? Where are the MR Job configs
present? how to access the MR job counters?
Similarly for YARN system entities to query the resource usage and the
containers stats(number of containers for different priority, time taken to
finish etc ...)
These were some of the queries which i have encountered from others...
> Retrospect container 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
>
> 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
