[
https://issues.apache.org/jira/browse/HDFS-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695368#comment-17695368
]
ASF GitHub Bot commented on HDFS-16938:
---------------------------------------
ayushtkn commented on PR #5445:
URL: https://github.com/apache/hadoop/pull/5445#issuecomment-1451064227
First patch isn't something to consider itself. Second one is like very
unrealistic in general, there aren't any things which we can blame above which
can consume time, they are some naive if checks or so, can't take this time...
I don't think we have a use case for now for this util, If my intent is just
for processQueueMessages, I will expose and just shoot that directly, rather
than doing the whole loop.
Changing the existing uses with this would be slowing down tests, which are
already above tolerable limits.
Lets hold it, and observe if we get something around this in future we can
circle back
> 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
