[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548447#comment-15548447
]
Rohith Sharma K S commented on YARN-5699:
-----------------------------------------
When I raised JIRA, my concern was too as Li mentioned. We have lost ability to
easily query yarn entities by adding few information in event info fields.
Currently, ATS does not support querying for event-info filter. And even if ATS
supports, it is again a burden for user to parse the information from different
events. For example,YARN container has information 3 different places. Firstly,
info field of entity about user, host detail, priority etc. Secondly, event
RM_CONTAINER_CREATED holds information about container start time and other.
Thirdly, event RM_CONTAINER_CREATED holds diagnostics, state and status.
So, I think entity related information better to publish at entity info level.
It is basically refactoring code.
> 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
