dolysis
/
rocksdb
mirror of https://github.com/facebook/rocksdb.git
3
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix rare WAL handling crash (#12899) 

Summary:
A crash test failure in log sync in DBImpl::WriteToWAL is due to a missed case in https://github.com/facebook/rocksdb/issues/12734. Just need to apply similar logic from DBImpl::SyncWalImpl to check for an already closed WAL (nullptr writer). This is extremely rare because it only comes from failed Sync on a closed WAL.

Pull Request resolved: https://github.com/facebook/rocksdb/pull/12899

Test Plan: watch crash test

Reviewed By: cbi42

Differential Revision: D60481652

Pulled By: pdillinger

fbshipit-source-id: 4a176bb6a53dcf077f88344710a110c2f946c386
This commit is contained in:
Peter Dillinger 2024-07-30 17:38:30 -07:00 committed by Facebook GitHub Bot
parent 55877d8893
commit 2595476541
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
db/db_impl/db_impl_write.cc
View File

@ -1484,9 +1484,14 @@ IOStatus DBImpl::WriteToWAL(const WriteThread::WriteGroup& write_group,
if (!io_s.ok()) { if (!io_s.ok()) {
break; break;
} }
io_s = log.writer->file()->Sync(opts, immutable_db_options_.use_fsync); // If last sync failed on a later WAL, this could be a fully synced
if (!io_s.ok()) { // and closed WAL that just needs to be recorded as synced in the
break; // manifest.
if (auto* f = log.writer->file()) {
io_s = f->Sync(opts, immutable_db_options_.use_fsync);
if (!io_s.ok()) {
break;
}
} }
} }
} }