[KAFKA-8324] User constructed RocksObjects leak memory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.1.0
• Fix Version/s: 2.3.0
• Component/s: streams
• Labels: kip
• Assignee: A. Sophie Blee-Goldman
• Reporter: A. Sophie Blee-Goldman
• Created: 03/May/19 23:31
• Updated: 11/Jul/19 16:03
• Resolved: 17/May/19 16:07

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. 

KIP-453: https://cwiki.apache.org/confluence/display/KAFKA/KIP-453%3A+Add+close%28%29+method+to+RocksDBConfigSetter 

Issue Links

• links to: GitHub Pull Request #6697
• mentioned in: Page Loading...