[
https://issues.apache.org/jira/browse/YARN-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535235#comment-16535235
]
Vrushali C edited comment on YARN-6767 at 7/6/18 7:01 PM:
----------------------------------------------------------
We need to handle collector fault tolerance, that is the case of collector
going down after it had come up. Tracked in YARN-7272
But the case of collector not being up itself in the first place needs to be
handled by the client framework.
was (Author: vrushalic):
We need to handle collector fault tolerance, that is the case of collector
going down after it had come up.
But the case of collector not being up itself in the first place needs to be
handled by the client framework.
> Timeline client won't be able to write when TimelineCollector is not up yet,
> or NM is down
> ------------------------------------------------------------------------------------------
>
> Key: YARN-6767
> URL: https://issues.apache.org/jira/browse/YARN-6767
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineclient
> Affects Versions: 3.0.0-alpha4
> Reporter: Haibo Chen
> Priority: Major
>
> As discussed in the call, when an application first starts to run, its
> corresponding TimelineCollector instance may not be up yet, or if the
> TimelineCollector goes down when node manager dies (TimelineCollector now
> runs as part of NM auxiliary services), the timeline client
> will not able to write entities. We need to address or mitigate the issue if
> possible, or at least call it out.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
