[
https://issues.apache.org/jira/browse/HDFS-16090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack updated HDFS-16090:
---------------------------------
Fix Version/s: 3.3.2
3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-3.3+ (It didn't go in clean against branch-3.2). Resolving.
Thanks for the improvement [~vjasani] . Thanks for reviews [~aajisaka] and
[~weichiu]
> Fine grained locking for datanodeNetworkCounts
> ----------------------------------------------
>
> Key: HDFS-16090
> URL: https://issues.apache.org/jira/browse/HDFS-16090
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> While incrementing DataNode network error count, we lock entire LoadingCache
> in order to increment network count of specific host. We should provide fine
> grained concurrency for this update because locking entire cache is redundant
> and could impact performance while incrementing network count for multiple
> hosts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
