[ https://issues.apache.org/jira/browse/HDFS-16163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated HDFS-16163: -------------------------------- Target Version/s: 3.4.0, 3.3.2 (was: 3.4.0, 3.2.3, 3.3.2) > Avoid locking entire blockPinningFailures map > --------------------------------------------- > > Key: HDFS-16163 > URL: https://issues.apache.org/jira/browse/HDFS-16163 > Project: Hadoop HDFS > Issue Type: Improvement > Reporter: Viraj Jasani > Assignee: Viraj Jasani > Priority: Major > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > In order for mover to exclude pinned blocks in subsequent iteration, we try > to put pinned blocks in a map of blockIds to set of Datanode sources. > However, while updating an entry of this map, we don't need to lock the > entire map. We can use fine-grained concurrency here. -- 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