[
https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881830#comment-13881830
]
Hudson commented on HDFS-4949:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #461 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/461/])
Move HDFS-4949 subtasks in CHANGES.txt to a new section under 2.4.0 release.
(wang: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1560528)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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.4.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Fix For: 2.4.0
>
> Attachments: HDFS-4949-consolidated.patch,
> 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-branch-2.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.5#6160)
