[
https://issues.apache.org/jira/browse/YARN-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-3616.
-------------------------------------
Resolution: Won't Fix
In ATSv2 weekly call, discussed for cleaning up JIRA which are not going
implement. Hence, closing the JIRA as Won't Fix.
Feel free to reopen if still same design approach exists.
> determine how to generate YARN container events
> -----------------------------------------------
>
> Key: YARN-3616
> URL: https://issues.apache.org/jira/browse/YARN-3616
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Naganarasimha G R
> Priority: Major
> Labels: YARN-5355
>
> The initial design called for the node manager to write YARN container events
> to take advantage of the distributed writes. RM acting as a sole writer of
> all YARN container events would have significant scalability problems.
> Still, there are some types of events that are not captured by the NM. The
> current implementation has both: RM writing container events and NM writing
> container events.
> We need to sort this out, and decide how we can write all needed container
> events in a scalable manner.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
