You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Rohan Pasalkar (JIRA)" <ji...@apache.org> on 2014/01/02 21:47:50 UTC

[jira] [Created] (HDFS-5711) Removing memory limitation of the Namenode by persisting Block - Block location mappings to disk.

Rohan Pasalkar created HDFS-5711:
------------------------------------

             Summary: Removing memory limitation of the Namenode by persisting Block - Block location mappings to disk.
                 Key: HDFS-5711
                 URL: https://issues.apache.org/jira/browse/HDFS-5711
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Rohan Pasalkar


This jira acts as an umbrella jira to track all the improvements we've done recently to improve Namenode's performance, responsiveness, and hence scalability. Those improvements include:
1. Incremental block reports (HDFS-395)
2. BlockManager.reportDiff optimization for processing block reports (HDFS-2477)
3. Upgradable lock to allow simutaleous read operation while reportDiff is in progress in processing block reports (HDFS-2490)
4. More CPU efficient data structure for under-replicated/over-replicated/invalidate blocks (HDFS-2476)
5. Increase granularity of write operations in ReplicationMonitor thus reducing contention for write lock (HDFS-2495)
6. Support variable block sizes
7. Release RPC handlers while waiting for edit log is synced to disk
8. Reduce network traffic pressure to the master rack where NN is located by lowering read priority of the replicas on the rack
9. A standalone KeepAlive heartbeat thread
10. Reduce Multiple traversals of path directory to one for most namespace manipulations
11. Move logging out of write lock section.





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)