[
https://issues.apache.org/jira/browse/HDFS-15618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363692#comment-17363692
]
Ahmed Hussein commented on HDFS-15618:
--------------------------------------
Submitted [^HDFS-15618-branch-2.10.002.patch] to fix the error in spotbugs .
It looks like {{TestJournalNodeRespectsBindHostKeys}} and {{TestBlockRecovery}}
were failing for several Months. I will track those failures and submit new
tickets if necessary.
There were some minor conflicts backporting the changes to 2.10:
* guava shading
* use of Lambda
* Use of concurrent Sets supported in JDK1.8+
[~kihwal]Can you please take a look at the [^HDFS-15618-branch-2.10.002.patch]?
> Improve datanode shutdown latency
> ---------------------------------
>
> Key: HDFS-15618
> URL: https://issues.apache.org/jira/browse/HDFS-15618
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
> Fix For: 3.2.2, 3.3.1, 3.4.0, 3.2.3
>
> Attachments: HDFS-15618-branch-2.10.001.patch,
> HDFS-15618-branch-2.10.002.patch, HDFS-15618-branch-3.3.004.patch,
> HDFS-15618.001.patch, HDFS-15618.002.patch, HDFS-15618.003.patch,
> HDFS-15618.004.patch
>
>
> The shutdown of Datanode is a very long latency. A block scanner waits for 5
> minutes to join on each VolumeScanner thread.
> Since the scanners are daemon threads and do not alter the block content, it
> is safe to ignore such conditions on shutdown of Datanode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
