[
https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HDFS-4949:
---------------------------------------
Attachment: caching-design-doc-2013-10-24.pdf
updated design doc.
Revisions:
* change future tense to present tense in some cases.
* grammar corrections
* update to reflect the fact that caching information is stored in
{{LocatedBlocks}} rather than {{BlockLocation}}
* move "cache expiry" feature to future work
* remove part about pools being in a configuration file (they are stored in the
edit log)
* rework API documentation to match current API
> 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)
