Gargi-jais11 commented on code in PR #9166:
URL: https://github.com/apache/ozone/pull/9166#discussion_r2454083998
##########
hadoop-hdds/common/src/main/resources/ozone-default.xml:
##########
@@ -465,6 +465,18 @@
<description>Socket timeout for Ozone client. Unit could be defined with
postfix (ns,ms,s,m,h,d)</description>
</property>
+ <property>
+ <name>ozone.client.elastic.byte.buffer.pool.max.size</name>
+ <value>16GB</value>
+ <tag>OZONE, CLIENT</tag>
+ <description>
+ The maximum total size of buffers that can be cached in the client-side
+ ByteBufferPool. This pool is used heavily during EC read and write
operations.
+ Setting a limit prevents unbounded memory growth in long-lived rpc
clients
+ like the S3 Gateway. Once this limit is reached, used buffers are not
+ put back to the pool and will be garbage collected.
Review Comment:
We can also call **System.gc()** to suggest that the garbage collector run
immediately. However, the Java Runtime makes the final decision.
According to the [Java
documentation](http://docs.oracle.com/javase/7/docs/api/java/lang/System.html#gc()).
So immediately deallocating buffer is not allowed by java. However if needed
we can use **System.gc()** to run garbage collector immediately.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
