[
https://issues.apache.org/jira/browse/HDDS-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823398#comment-17823398
]
Pratyush Bhatt commented on HDDS-10043:
---------------------------------------
Hi [~szetszwo] , yeah this was my test code, below is the log of the value of
this property printed via the test code( I have set this
ozone.client.stream.buffer.increment to 65537B as per your suggestion):
{code:java}
2024-03-05 02:52:15,660|INFO|Thread-44|machine.py:205 -
run()||GUID=0b4ede0a-5838-49ae-a735-d1ff24041b56|Value of
ozone.client.stream.buffer.increment is : 65537B {code}
Now its throwing a different kind of error:
{code:java}
Test set: org.ozonehsync.TestOzoneHsync
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 22.144 sec <<<
FAILURE!
checkOzoneHsync(org.ozonehsync.TestOzoneHsync) Time elapsed: 18.964 sec <<<
ERROR!
java.io.IOException: java.lang.UnsupportedOperationException: Buffer size and
increment mismatched: bufferSize = 65536 but increment = 65537
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.handleWrite(KeyOutputStream.java:258)
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.write(KeyOutputStream.java:228)
at
org.apache.hadoop.ozone.client.io.OzoneOutputStream.write(OzoneOutputStream.java:92)
at
org.apache.hadoop.fs.ozone.OzoneFSOutputStream.write(OzoneFSOutputStream.java:50)
at
org.apache.hadoop.fs.FSDataOutputStream$PositionCache.write(FSDataOutputStream.java:62)
at java.io.DataOutputStream.write(DataOutputStream.java:107)
at java.io.FilterOutputStream.write(FilterOutputStream.java:97)
at org.ozonehsync.TestOzoneHsync.checkOzoneHsync(TestOzoneHsync.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {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]
