rocksdb icon indicating copy to clipboard operation
rocksdb copied to clipboard

Published 20 hours ago • verified publisher icon facebook

The bug of rocksdb env

Open wanglinke521 opened this issue 1 year ago • 1 comments

Note: Please use Issues only for bug reports. For questions, discussions, feature requests, etc. post to dev group: https://groups.google.com/forum/#!forum/rocksdb or https://www.facebook.com/groups/rocksdb.dev

  • When writing data through the env provided by rocksdb, NewWritableFile is called, but NewRandomAccessFile is called at the same time. What is the reason?
  • Each NewWritableFile will actively release resources after the call is completed, but NewRandomAccessFile will wait until all writes are completed before releasing resources. This will cause the NewRandomAccessFile function to continuously create read objects when the amount of data written is too large. Memory will continue to increase. Has this bug always existed? Is there any solution?

wanglinke521 avatar Dec 15 '23 06:12 wanglinke521

Can you provide a code pointer for this bug you were referring to? I didn't find where we are doing this in our code base.

jowlyzhang avatar Feb 02 '24 22:02 jowlyzhang