hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4949) Centralized cache management in HDFS
Date Fri, 25 Oct 2013 16:41:04 GMT

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

Suresh Srinivas commented on HDFS-4949:
---------------------------------------

Given that the merge vote thread has been started, can someone post details about what functionality
from original design has been completed and what is pending? Looks like the current functionality
does not cover quota management. Any other features pending?

> Centralized cache management in HDFS
> ------------------------------------
>
>                 Key: HDFS-4949
>                 URL: https://issues.apache.org/jira/browse/HDFS-4949
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: datanode, namenode
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: caching-design-doc-2013-07-02.pdf, caching-design-doc-2013-08-09.pdf,
caching-design-doc-2013-10-24.pdf, caching-testplan.pdf, HDFS-4949-consolidated.patch
>
>
> HDFS currently has no support for managing or exposing in-memory caches at datanodes.
This makes it harder for higher level application frameworks like Hive, Pig, and Impala to
effectively use cluster memory, because they cannot explicitly cache important datasets or
place their tasks for memory locality.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message