[ 
https://issues.apache.org/jira/browse/HDFS-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695362#comment-17695362
 ] 

ASF GitHub Bot commented on HDFS-16938:
---------------------------------------

virajjasani commented on PR #5445:
URL: https://github.com/apache/hadoop/pull/5445#issuecomment-1451015537

   Another way I am able to repro consistently:
   
   ```
   diff --git 
a/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java
 
b/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java
   index e9f424604b4..9b17a126da1 100755
   -

> Utility to trigger heartbeat and wait until BP thread queue is fully processed
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-16938
>                 URL: https://issues.apache.org/jira/browse/HDFS-16938
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>
> As a follow-up to HDFS-16935, we should provide utility to trigger heartbeat 
> and wait until BP thread queue is fully processed. This would ensure 100% 
> consistency w.r.t active namenode being able to receive bad block reports 
> from the given datanode. This utility would resolve flakes for the tests that 
> rely on namenode's awareness of the reported bad blocks by datanodes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
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