hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3616) determine how to generate YARN container events
Date Wed, 13 May 2015 23:22:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542900#comment-14542900

Sangjin Lee commented on YARN-3616:

Yes, I agree that we should emit some events from RM that NM cannot handle. I think we just
need to enumerate clearly what events will be emitted by RM so there is no duplication.

> 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
> 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

View raw message