[
https://issues.apache.org/jira/browse/HDFS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129486#comment-13129486
]
Uma Maheswara Rao G commented on HDFS-2452:
-------------------------------------------
Thanks a lot for taking a look.
Ok fine...I thought to test exact case even after one round retry.
I will not remove complete wait there, because Test may complete before exactly
spawning the new thread. So, i am planning to put wait of 100ms.
{quote}
Can you mock datanode.getXceiverCount() to throw OutOfMemoryError on the second
call. That way the error will come from DataXceiver.run()
{quote}
Here the problem is, DataXceiver thread already handled the Throwable there.
So, the exception will be handled silently and log the error. So, it will not
reach to our exception block.
{code}
catch (Throwable t) {
LOG.error(datanode.dnRegistration + ":DataXceiver, at " +
s.toString(), t);
}
{code}
Thanks
Uma
> OutOfMemoryError in DataXceiverServer takes down the DataNode
> -------------------------------------------------------------
>
> Key: HDFS-2452
> URL: https://issues.apache.org/jira/browse/HDFS-2452
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 0.22.0
> Reporter: Konstantin Shvachko
> Assignee: Uma Maheswara Rao G
> Fix For: 0.22.0
>
> Attachments: HDFS-2452-22branch.1.patch, HDFS-2452-22branch.patch
>
>
> OutOfMemoryError brings down DataNode, when DataXceiverServer tries to spawn
> a new data transfer thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
