Manifest is created in read only mode
- Dominant language
- C++
- Stars
- 32.1k
- Forks
- 6.9k
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
I'm using RocksDB version 6.8.1, where after a crash, I open the database in read-only mode to read data for recovery, then the database is closed and opened in write mode.
After a crash, I got a failure to open the database due to ```No such file or directory While open a file for random read: rocksdbdata/000075.ldb: No such file or directory```
I followed the LOGs where I saw that a LOG file that belongs to a read-only mode is reporting also the creation of a Manifest
`2022/07/26-14:22:47.656806 7f1dbdb9b280 [_impl/db_impl_readonly.cc:23] Opening the db in read only mode
2022/07/26-14:22:47.656900 7f1dbdb9b280 [rsion_set.cc:4413] Recovering from manifest file: /concord/rocksdbdata/MANIFEST-000071`
after some lines
`2022/07/26-14:22:48.002199 7f1dbdb9b280 [rsion_set.cc:3826] Creating manifest 77`
The 77 manifest contains the 75.sst file that is deleted as part of Manifest 71.
### Expected behavior
RO should not create Manifest.
### Actual behavior
RO creating a Manifest and updating CURRENT
### Steps to reproduce the behavior
N/A
Contributor guide
Assessment
This issue has not been assessed yet.