Zhijie Shen commented on YARN-3942:

Yeah, I prefer creating a TimelineEntityFileClient to modifying the current 
TimelineClientImp, because it should minimize the affect on existing code path. 
However, I'm afraid no matter which way we chose, we cannot make the change 
seamless to users.  We cannot avoid the additional step at the client side to 
set app/app-attempt ID, can we? At Hive/Tez client (and other potential app 
client), you also have to switch the context app/app-attempt ID once the client 
detect a new YARN app/app-attempt is created. Therefore, if some application 
wants to make use of it, it will also involve code change at the user land.

BTW, why do you need app-attempt ID? Is the log file on the basis of app or 

> 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