[
https://issues.apache.org/jira/browse/HADOOP-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660067#action_12660067
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4962:
------------------------------------------------
> I'm able to consistently reproduce the same issue in 0.19.0.
Do you mean the 0.19.0 release? HADOOP-4679 has been committed to 0.18 branch
and above. You will see it if you checkout the current 0.19 branch, or you
have to wait for 0.19.1 release. We cannot change 0.19.0 release anymore since
it is already released.
> HADOOP-4679 to be fixed for branches >= 0.19
> --------------------------------------------
>
> Key: HADOOP-4962
> URL: https://issues.apache.org/jira/browse/HADOOP-4962
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Sean Knapp
>
> HADOOP-4679 applies to 0.18.3 only. I'm able to consistently reproduce the
> same issue in 0.19.0.
> For reference, our Datanodes use 4 independent drives. When we pull any of
> them, the Datanode begins logging hundreds of the following message per
> second:
> {quote}
> 2008-12-31 03:33:48,627 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
> Waiting for threadgroup to exit, active threads is 2
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
