hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery
Date Wed, 25 Feb 2015 08:38:06 GMT

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

Robert Kanter commented on YARN-3039:
-------------------------------------

Sorry for not commenting earlier.  Thanks for taking this up [~djp].

Not using YARN-913 is fine if it's not going to make sense.  I haven't looked too closely
at it either; it just sounded like it might be helpful here.  

One comment on the patch:
- Given that a particular NM is only interested in the Applications that are running on it,
is there some way to have it only receive the aggregator info for those apps?  This would
decrease the amount of "throw away" data that gets sent.  

Also, can you update the design doc?  Looking at the patch, it seems like some things have
changed.  (e.g. it's using protobufs instead of REST; which I think makes more sense here
anyway).

> [Aggregator wireup] Implement ATS writer service discovery
> ----------------------------------------------------------
>
>                 Key: YARN-3039
>                 URL: https://issues.apache.org/jira/browse/YARN-3039
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Junping Du
>         Attachments: Service Binding for applicationaggregator of ATS (draft).pdf, YARN-3039-no-test.patch
>
>
> Per design in YARN-2928, implement ATS writer service discovery. This is essential for
off-node clients to send writes to the right ATS writer. This should also handle the case
of AM failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message