[ 
https://issues.apache.org/jira/browse/HDFS-16511?focusedWorklogId=747658&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-747658
 ]

ASF GitHub Bot logged work on HDFS-16511:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Mar/22 08:18
            Start Date: 25/Mar/22 08:18
    Worklog Time Spent: 10m 
      Work Description: tomscut commented on a change in pull request #4085:
URL: https://github.com/apache/hadoop/pull/4085#discussion_r835043287



##########
File path: 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/fsdataset/impl/TestFsDatasetImpl.java
##########
@@ -602,6 +605,54 @@ public void run() {}
         + "volumeMap.", 0, totalNumReplicas);
   }
 
+  @Test(timeout = 30000)
+  public void testCurrentWriteAndDeleteBlock() throws Exception {
+    // Feed FsDataset with block metadata.
+    final int numBlocks = 1000;
+    final int threadCount = 10;
+    // Generate data blocks.
+    ExecutorService pool = Executors.newFixedThreadPool(threadCount);
+    List<Future<?>> futureList = new ArrayList<>();
+    for (int i = 0; i < threadCount; i++) {
+      Thread thread = new Thread() {
+        @Override
+        public void run() {
+          try {
+            for (int i = 0; i < numBlocks; i++) {
+              String bpid = BLOCK_POOL_IDS[numBlocks % BLOCK_POOL_IDS.length];

Review comment:
       > Yes, this means random write to a block pool.like 
testRemoveTwoVolumes().
   
   But the bpid here always looks like "bpid-0", right?




-- 
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: 747658)
    Time Spent: 1h  (was: 50m)

> Change some frequent method lock type in ReplicaMap.
> ----------------------------------------------------
>
>                 Key: HDFS-16511
>                 URL: https://issues.apache.org/jira/browse/HDFS-16511
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs
>            Reporter: Mingxiang Li
>            Assignee: Mingxiang Li
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In HDFS-16429 we make LightWeightResizableGSet to be thread safe, and  In 
> HDFS-15382 we have split lock to block pool grain locks.After these 
> improvement, we can change some method to acquire read lock replace to 
> acquire write lock.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to