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

Jason Lowe commented on YARN-4219:
----------------------------------

Shouldn't we commit some form of YARN-3942 before committing this?  I got the 
impression this was an underlying storage to be used by the 
EntityFileTimelineStore, or is there a use-case for this outside of the v1.5 
core code in YARN-3942?

Patch looks pretty good except for one thing I noticed: The pom file should not 
have hardcoded versions in it.  It should omit the versions and leave it up to 
hadoop-project/pom.xml to define that.  Otherwise we risk having different 
portions of code needing different versions of the same dependency.


> New levelDB cache storage for timeline v1.5
> -------------------------------------------
>
>                 Key: YARN-4219
>                 URL: https://issues.apache.org/jira/browse/YARN-4219
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.8.0
>            Reporter: Li Lu
>            Assignee: Li Lu
>         Attachments: YARN-4219-trunk.001.patch, YARN-4219-trunk.002.patch, 
> YARN-4219-trunk.003.patch
>
>
> We need to have an "offline" caching storage for timeline server v1.5 after 
> the changes in YARN-3942. The in memory timeline storage may run into OOM 
> issues when used as a cache storage for entity file timeline storage. We can 
> refactor the code and have a level db based caching storage for this use 
> case. 



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

Reply via email to