hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4219) New levelDB cache storage for timeline v1.5
Date Sat, 14 Nov 2015 00:52:11 GMT

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

Li Lu commented on YARN-4219:
-----------------------------

I noticed one problem for the current ATS v1.5's caching policy is that a cache storage may
still be accessed after the cache is evicted. A quick fix is on the storage side: we can synchronously
stop the storage service, and check if the service is already stopped on each storage request.
We can build a more graceful cache evicting mechanism in future. 

> 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-YARN-4265.001.patch, 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)

Mime
View raw message