Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.22.0
-
None
-
None
-
None
Description
The HDFS Name service currently uses a single Namenode which limits its scalability. This is a master jira to track sub-jiras to address this problem.
Attachments
Issue Links
- incorporates
-
HDFS-1052 HDFS scalability with multiple namenodes
- Resolved
- relates to
-
HDFS-1162 Reduce the time required for a checkpoint
- Resolved
-
HDFS-1499 mv the namenode NameSpace and BlocksMap to hbase to save the namenode memory
- Resolved
-
HADOOP-6713 The RPC server Listener thread is a scalability bottleneck
- Closed
-
HDFS-1068 Reduce NameNode GC by reusing HdfsFileStatus objects in RPC handlers
- Patch Available