[
https://issues.apache.org/jira/browse/HDDS-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819925#comment-17819925
]
Pratyush Bhatt commented on HDDS-10043:
---------------------------------------
Hi [~szetszwo] , earlier it was 0, now I have switched it to 64k, still it
doesnt solve the issue.
{code:java}
/opt/cloudera/parcels/CDH/bin/ozone getconf -confKey
ozone.client.stream.buffer.increment
64k {code}
Before HDDS-9843 was merged, I was able to do writeOps only on around 300
FSDataOutputStream, after that it got increased to around ~450. After the merge
I dont get _OutOfMemoryError,_ but I get something like this:
{code:java}
checkOzoneHsync(org.ozonehsync.TestOzoneHsync): failed to allocate 4194304
byte(s) of direct memory (used: 1778384896, max: 1778384896) {code}
> java.lang.OutOfMemoryError on FSDataOutputStream write ops
> ----------------------------------------------------------
>
> Key: HDDS-10043
> URL: https://issues.apache.org/jira/browse/HDDS-10043
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Client
> Reporter: Pratyush Bhatt
> Priority: Major
>
> Seems like FSDataOutputStream utilise higher heap memory.
> Doing write Ops in ~300 FSDataOutputStream objects sequentially is causing
> {color:#FF0000}_java.lang.OutOfMemoryError: Java heap space_
> {color}{color:#FF0000}error. {color}
> While the FSDataOutputStream on HDFS doesn't throws heap issues, tried with
> ~3000 objects on same Environment, works fine.
> Note: Both the tests were performed in same environment.
> Client is a Kube container, specs:
> {code:java}
> limits:
> cpu: "1"
> ephemeral-storage: 5G
> memory: 300M
> requests:
> cpu: 200m
> ephemeral-storage: 1G
> memory: 200M {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
