hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2362) More Improvements on NameNode Scalability
Date Wed, 08 Feb 2012 01:48:59 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203121#comment-13203121
] 

Eli Collins commented on HDFS-2362:
-----------------------------------

Not for 23.1, which is getting cut soon. We'll merge the PB changes (Jitendra has a branch
for this) and BR scalability changes when 23.1 has branched. 
                
> More Improvements on NameNode Scalability
> -----------------------------------------
>
>                 Key: HDFS-2362
>                 URL: https://issues.apache.org/jira/browse/HDFS-2362
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Hairong Kuang
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message