[
https://issues.apache.org/jira/browse/HDFS-16163?focusedWorklogId=637677&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-637677
]
ASF GitHub Bot logged work on HDFS-16163:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Aug/21 04:40
Start Date: 13/Aug/21 04:40
Worklog Time Spent: 10m
Work Description: virajjasani commented on pull request #3296:
URL: https://github.com/apache/hadoop/pull/3296#issuecomment-898186659
Sure @ferhui, Thank you. Let me retrigger tests. On the side note, I am
working on resolving two flakies: #3280 and #3235
Thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 637677)
Time Spent: 1h 10m (was: 1h)
> 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
