[
https://issues.apache.org/jira/browse/HDFS-7396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212469#comment-14212469
]
Chris Nauroth commented on HDFS-7396:
-------------------------------------
bq. Whenever we experimented with improving concurrency, the limiting factor
was the garbage collection overhead.
I also would be interested in seeing more information on this. We've been
updating our recommendations for garbage collection tuning recently. It would
be interesting for us to compare notes.
I'm also curious if you've tried any experiments running with the G1 collector.
I haven't tried it in several years. When I tried it, it was still very
experimental, so I ended up hitting too many bugs to run it in production.
Perhaps it has stabilized by now.
> Revisit synchronization in Namenode
> -----------------------------------
>
> Key: HDFS-7396
> URL: https://issues.apache.org/jira/browse/HDFS-7396
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
>
> HDFS-2106 separated block management to a new package from namenode. As part
> of it, some code was refactored to new classes such as DatanodeManager,
> HeartbeatManager, etc. There are opportunities for improve locking in
> namenode while currently the synchronization in namenode is mainly done by a
> single global FSNamesystem lock.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
