[
https://issues.apache.org/jira/browse/HDFS-15618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215452#comment-17215452
]
Kihwal Lee commented on HDFS-15618:
-----------------------------------
In production, there is no harm in exiting after waiting for 5 seconds. But in
junit, as you pointed out, it might cause more failures when the environment is
slow. We can set the timeout to something like 30 seconds in the mini dfs
cluster's base config.
> 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
> Attachments: HDFS-15618.001.patch, HDFS-15618.002.patch,
> HDFS-15618.003.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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
