[
https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387561#comment-14387561
]
Sangjin Lee commented on YARN-3334:
-----------------------------------
I'm +1 with the simpler approach mentioned here. There are races in the
getTimelineClient() method for sure, but if we take this approach, the problem
is moot.
> [Event Producers] NM TimelineClient life cycle handling and container metrics
> posting to new timeline service.
> --------------------------------------------------------------------------------------------------------------
>
> Key: YARN-3334
> URL: https://issues.apache.org/jira/browse/YARN-3334
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: YARN-2928
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: YARN-3334-demo.patch, YARN-3334-v1.patch,
> YARN-3334-v2.patch, YARN-3334-v3.patch
>
>
> After YARN-3039, we have service discovery mechanism to pass app-collector
> service address among collectors, NMs and RM. In this JIRA, we will handle
> service address setting for TimelineClients in NodeManager, and put container
> metrics to the backend storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
