Skip to content

Commit

Permalink
revise upper_limit handling in datastore::update_min_epoch_id()
Browse files Browse the repository at this point in the history
  • Loading branch information
t-horikawa committed Dec 19, 2024
1 parent 10be3bc commit 1e95d39
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions src/limestone/datastore.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,8 @@ void datastore::update_min_epoch_id(bool from_switch_epoch) { // NOLINT(readabi
// as no WAL writer has been tool place from max_finished_epoch to upper_limit and
// epoch file has updated with max_finished_epoch.
to_be_epoch = upper_limit;
} else {
to_be_epoch = epoch_id_record_finished_.load();
}
// In `informed_epoch_`, the update restriction based on the `from_switch_epoch` condition is intentionally omitted.
// Due to the interface specifications of Shirakami, it is necessary to advance the epoch even if the log channel
Expand Down

0 comments on commit 1e95d39

Please sign in to comment.