[GitHub] [bookkeeper] hangc0276 commented on issue #3734: RocksDB: segfault in org.rocksdb.WriteBatch::delete called from org.apache.bookkeeper.bookie.storage.ldb.EntryLocationIndex#removeOffsetFromDeletedLedgers

["hangc0276 (via GitHub)" <gi...@apache.org>]

hangc0276 commented on issue #3734:
URL: https://github.com/apache/bookkeeper/issues/3734#issuecomment-1407338171

   Hi @dlg99, thanks for raising this issue. From the information you provided, the segfault issue seems caused by `deleteRange` operation.
   
   > After some research I have a gut feeling that the problem is related to fix of "a bug in iterator refresh which could segfault for DeleteRange users" https://github.com/facebook/rocksdb/pull/10739
   
   RocksDB PR 10739 looks like not fix the issue we encountered. That issue was introduced since RocksDB 7.7 https://github.com/facebook/rocksdb/pull/10739#issuecomment-1381241853
   
   We need to get the core dump file to investigate the root cause of the RocksDB segfault issue.
   
   I suggest reverting the PR https://github.com/apache/bookkeeper/pull/3653 on branch-4.14 and branch-4.15. For the master branch, we keep the PR and try to upgrade the RocksDB version to 7.8+ to see if the segfault issue is resolved.
   
   @merlimat @eolivelli Do you have any ideas?


-- 
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: commits-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org