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

Junping Du commented on YARN-4265:
----------------------------------

I just commit YARN-4234. [~gtCarrera9], would you rebase your patch on latest 
trunk branch? Thanks!
Hi [~jlowe], I saw your comments above: "This looks like most of the patch is a 
copy of the entity timeline store from YARN-3942 with a few edits, so I'm sorta 
reviewing my own code here. As such I did a diff of the patch from this JIRA 
and the one from YARN-3942 so I could focus on what's changed. I'll defer to 
others to review the parts that are identical to YARN-3942. Eventually I can 
see this being a superset of YARN-3942, since it can cache to memory and either 
cache everything or a subset based on what the plugins decide." Are you OK with 
continue the review effort going with this patch? Or you have some other 
preferences?


> Provide new timeline plugin storage to support fine-grained entity caching
> --------------------------------------------------------------------------
>
>                 Key: YARN-4265
>                 URL: https://issues.apache.org/jira/browse/YARN-4265
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Li Lu
>            Assignee: Li Lu
>         Attachments: YARN-4265-trunk.poc_001.patch, 
> YARN-4265.YARN-4234.001.patch, YARN-4265.YARN-4234.002.patch
>
>
> To support the newly proposed APIs in YARN-4234, we need to create a new 
> plugin timeline store. The store may have similar behavior as the 
> EntityFileTimelineStore proposed in YARN-3942, but cache date in cache id 
> granularity, instead of application id granularity. Let's have this storage 
> as a standalone one, instead of updating EntityFileTimelineStore, to keep the 
> existing store (EntityFileTimelineStore) stable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to