File tree Expand file tree Collapse file tree
storage/src/journal/contiguous Expand file tree Collapse file tree Original file line number Diff line number Diff line change 4040//!
4141//! # Metadata
4242//!
43- //! Metadata consists of two optional keys:
43+ //! Metadata contains the following keys:
4444//! - PRUNING_BOUNDARY_KEY: Stores the pruning boundary as a u64 when it's mid-section (not a
4545//! multiple of items_per_blob). Absent from legacy journals or when the boundary is
4646//! section-aligned, since it can be derived from the oldest blob.
47- //! - RECOVERY_WATERMARK_KEY: Stores the last logical size at which the fixed journal's entries and
48- //! metadata were synced as a coherent recovery checkpoint for external consumers. Fixed-journal
49- //! recovery does not use this value to decide whether short blobs are corrupt. Absent on journals
50- //! created before this key was added; those journals recover from the newest retained blob using
51- //! the old rollover-sync invariant, then write the key before accepting new appends.
47+ //! - RECOVERY_WATERMARK_KEY: Stores a lower bound on the last logical size at which the fixed
48+ //! journal's entries and metadata were synced as a coherent recovery checkpoint for external
49+ //! consumers. The key is durably written during initialization for any journal last opened before
50+ //! this key was introduced.
5251//!
5352//! RECOVERY_WATERMARK_KEY is mainly useful when this journal is used as an index for a layered
5453//! journal, such as the variable journal's offsets. Standalone fixed journals do not need it to
You can’t perform that action at this time.
0 commit comments