Details
-
Bug
-
Resolution: Fixed
-
Critical
-
3.0
-
Security Level: Public
-
None
-
Untriaged
-
3
-
Unknown
-
June 30 - July 18
Description
A snapshot can be created explicitly by calling snapshot API and only allows us to perform read-only operations. A snapshot is destroyed if its corresponding database handle is closed.
Creating a snapshot instance should NOT corrupt the WAL index used by the writer. Otherwise, it will overwrite the current WAL entries with the stale WAL docs from the old header of the snapshot.
Note that we maintain a single WAL index per file (NOT per handle). To address this issue, we need to restore the read-only WAL index separately for a given snapshot.
Attachments
For Gerrit Dashboard: MB-10485 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
35001,4 | MB-10485-prereq: Add Read-Only option to forestdb | master | forestdb | Status: MERGED | +2 | +1 |
35173,8 | MB-10485 Snapshot Support in ForestDB | master | forestdb | Status: MERGED | +2 | +1 |
35320,1 | Revert "MB-10485 Snapshot Support in ForestDB" | master | forestdb | Status: MERGED | +2 | +1 |
36007,9 | MB-10485: Snapshot full support in forestdb | master | forestdb | Status: MERGED | +2 | +1 |