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

Jason Lowe commented on YARN-3942:
----------------------------------

bq. Since we know the file size to be read, could we return a message saying 
something like "scanning file size FOO. Expect BAR latency"?

I'm not a UI expert, but given the timeline store is just a REST backend to the 
real UI this seems tricky to do in practice.  The UI javascript is doing a 
bunch of separate GETs to the various REST endpoints and expecting the results, 
but we'd have to return something else that says "I'm not done yet" and expect 
the UI to do something sane with that.  If we do this over the normal endpoints 
it will break the timelineserver API for existing clients.  Granted, we're 
already sorta breaking it by not supporting some cross-app queries that were 
supported in the past.

> 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
(v6.3.4#6332)

Reply via email to