[
https://issues.apache.org/jira/browse/KAFKA-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sophie Blee-Goldman updated KAFKA-8324:
---------------------------------------
Description:
Some of the RocksDB options a user can set when extending RocksDBConfigSetter
take Rocks objects as parameters. Many of these – including potentially large
objects like Cache and Filter – inherit from AbstractNativeReference and must
be closed explicitly in order to free the memory of the backing C++ object.
However the user has no way of closing any objects they have created in
RocksDBConfigSetter, and we do not ever close them for them.
was:
Some of the RocksDB options a user can set when extending RocksDBConfigSetter
take Rocks objects as parameters. Many of these--including potentially large
objects like Cache and Filter-- inherit from AbstractNativeReference and must
be closed explicitly in order to free the memory of the backing C++ object.
However the user has no way of closing any objects they have created in
RocksDBConfigSetter, and we do not ever close them for them.
> User constructed RocksObjects leak memory
> -----------------------------------------
>
> Key: KAFKA-8324
> URL: https://issues.apache.org/jira/browse/KAFKA-8324
> Project: Kafka
> Issue Type: Bug
> Reporter: Sophie Blee-Goldman
> Priority: Major
>
> Some of the RocksDB options a user can set when extending RocksDBConfigSetter
> take Rocks objects as parameters. Many of these – including potentially large
> objects like Cache and Filter – inherit from AbstractNativeReference and must
> be closed explicitly in order to free the memory of the backing C++ object.
> However the user has no way of closing any objects they have created in
> RocksDBConfigSetter, and we do not ever close them for them.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
