[
https://issues.apache.org/jira/browse/HDFS-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695829#comment-13695829
]
Suresh Srinivas commented on HDFS-4940:
---------------------------------------
[~rvs], we had exchange few emails about this. With Xmx == Xms, do you still
see namenode running OOME? Also I had suggested setting bigger PermSize on the
client side, did you get a chance to test that?
bq. so I think the issue here is that the RPC layer reads 4 bytes from the
client, and allocates a buffer of that size, no matter how big it is.
While it is possible, the likelihood of some request sending incorrect size in
these tests is probably low. I am not sure if this is the cause.
> namenode OOMs under Bigtop's TestCLI
> ------------------------------------
>
> Key: HDFS-4940
> URL: https://issues.apache.org/jira/browse/HDFS-4940
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Roman Shaposhnik
> Priority: Blocker
> Fix For: 2.1.0-beta
>
>
> Bigtop's TestCLI when executed against Hadoop 2.1.0 seems to make it OOM
> quite reliably regardless of the heap size settings. I'm attaching a heap
> dump URL. Alliteratively anybody can just take Bigtop's tests, compiled them
> against Hadoop 2.1.0 bits and try to reproduce it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
