[
https://issues.apache.org/jira/browse/HDFS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135898#comment-13135898
]
Uma Maheswara Rao G commented on HDFS-2452:
-------------------------------------------
Hi Konstantin,
I just compared the code with trunk and 0.22 branch. I don't see any
difference, except getInputStream stub and there is no sleeps as well!.
I think, i he may be pointing about source code 30sec sleep or may be about
testcase timeout. That will be the failure case. If CountDownLatch does not
decrement the count then, latch.await() may wait forever. So , to avaoid this,
we gave 30000ms as testcase timeout. This will be the failure case.
If that is the case, we need to correct the actual testcase problem first. Why
it is not throwing the OutOfMemory Error from aspectj mocks and did he provided
any trace? If you get any trace please provide, i will take a look.
one more point is, some one started looking on AspectJ on trunk? if yes, can
you share the options to run the aspectJ on trunk if you have idea?
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, 0.23.0, 0.24.0
> Reporter: Konstantin Shvachko
> Assignee: Uma Maheswara Rao G
> Fix For: 0.22.0, 0.23.0, 0.24.0
>
> Attachments: HDFS-2452-22Branch.2.patch, HDFS-2452-22branch.1.patch,
> HDFS-2452-22branch.patch, HDFS-2452-22branch.patch, HDFS-2452-22branch.patch,
> HDFS-2452-22branch.patch, HDFS-2452-22branch_with-around_.patch,
> HDFS-2452-22branch_with-around_.patch, HDFS-2452-Trunk-src-fix.patch,
> HDFS-2452-Trunk.patch, HDFS-2452.patch, HDFS-2452.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
