Jason Lowe commented on YARN-3942:

I think so.  We can probably create a new TimelineClient that stores to HDFS 
files based on how yarn.timeline-service.entity-file-store.summary-entity-types 
is configured.  However I'm not sure if YARN can automatically replace timeline 
clients being requested with this one, as the client needs to know the 
application ID when putting domains and the application attempt ID when posting 
entities.  So one approach is to have YARN provide something like a 
TimelineEntityFileClient, which is a TimelineClient, but Tez and other app 
frameworks would have to explicitly ask for it themselves and provide the 
appropriate application ID/app attempt ID upon construction of the client.

Let me know if that sounds OK if there's an idea of how YARN can seamlessly 
provide this alternative client instead of TimelineClientImpl when 
TimelineClient.createTimelineClient is called.

> Timeline store to read events from HDFS
> ---------------------------------------
>                 Key: YARN-3942
>                 URL: https://issues.apache.org/jira/browse/YARN-3942
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: timelineserver
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: YARN-3942.001.patch
> This adds a new timeline store plugin that is intended as a stop-gap measure 
> to mitigate some of the issues we've seen with ATS v1 while waiting for ATS 
> v2.  The intent of this plugin is to provide a workable solution for running 
> the Tez UI against the timeline server on a large-scale clusters running many 
> thousands of jobs per day.

This message was sent by Atlassian JIRA

Reply via email to