Details
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
HDFS-9957 HDFS's use of mlock() is not portable
- Open
-
HDFS-5203 Concurrent clients that add a cache directive on the same path may prematurely uncache from each other.
- Resolved
-
HDFS-5385 Caching RPCs are AtMostOnce, but do not persist client ID and call ID to edit log.
- Resolved
-
HDFS-5388 Loading fsimage fails to find cache pools during namenode startup.
- Resolved
-
HDFS-5195 Prevent passing null pointer to mlock and munlock.
- Resolved
-
HDFS-5266 ElasticByteBufferPool#Key does not implement equals.
- Resolved
-
HDFS-5269 Attempting to remove a cache directive fails with NullPointerException.
- Resolved
-
HDFS-5313 NameNode hangs during startup trying to apply OP_ADD_PATH_BASED_CACHE_DIRECTIVE.
- Resolved
-
HDFS-5373 hdfs cacheadmin -addDirective short usage does not mention -replication parameter.
- Resolved
-
YARN-1488 Allow containers to delegate resources to another container
- Open
-
HDFS-4953 enable HDFS local reads via mmap
- Resolved
-
HDFS-5197 Document dfs.cachereport.intervalMsec in hdfs-default.xml.
- Resolved
- relates to
-
HIVE-6347 ZeroCopy read path for ORC RecordReader
- Resolved
-
HDFS-2832 Enable support for heterogeneous storages in HDFS - DN as a collection of storages
- Closed
-
HDFS-16650 Optimize the cost of obtaining timestamps in Centralized cache management
- In Progress
-
HDFS-5202 Support Centralized Cache Management on Windows.
- Closed