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

Li Lu commented on YARN-4265:
-----------------------------

bq. Can we provide a default one (could be simple) for built-in YARN 
applications, i.e. distributed shell?
We can certainly do that, given that the new APIs are in and we've got this 
patch. Since this is a separate work than introducing the whole new storage (as 
in this JIRA), maybe we can address this as a new JIRA? I can start off doing 
that right away. 

bq.  Looks like we still need to make effort on checking the whole 
synchronization mechanism. Isn't it?
I checked all synchronization logic a few times before I submit the original 
patch. We're using fine-grained locking in this patch, so yes it's more error 
pruning. I'll check again later on and fix any problem I discovered. Feel free 
to raise up any concerns in your review. Thanks! 

> 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.001.patch, YARN-4265-trunk.002.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