PragmaTwice commented on issue #639:
URL: 
https://github.com/apache/incubator-kvrocks/issues/639#issuecomment-1173006654

   > I think maybe it's a false leak report. Coz the main thread will write the 
memtable and convert the memtable to immutable state after it reached the max 
limit, then RocksDB background will read the memtable and flush them into disk. 
So it should be expected behavior that have the data race between main thread 
and background thread, but will not cause problem.
   > 
   > HDYT? @ShooterIT @PragmaTwice @tisonkun
   
   Seems the writing in kvrocks main thread and the reading in rocksdb 
background thread occurs at the same time and in the same memory location? 
Won't this be a problem?


-- 
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]

Reply via email to