You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2016/07/11 17:21:14 UTC
[jira] [Updated] (YARN-3616) determine how to generate YARN
container events
[ https://issues.apache.org/jira/browse/YARN-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joep Rottinghuis updated YARN-3616:
-----------------------------------
Labels: YARN-5355 (was: )
> 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
> 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
(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