Skip to content

Conversation

timvisee
Copy link
Member

Tracked in: #6157

Show a warning if the number of internal point mappings does not match with the number of versions. Their counts should normally be equal.

If a crash happens during flush, new versions may only be partially written or not at all. In such case we can expect the list of versions to be shorter.

This shows a warning to make us aware of this having happened, potentially allowing is to debug better. Under normal circumstances, the WAL should always recover this situation.

All Submissions:

  • Contributions should target the dev branch. Did you create your branch from dev?
  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

  1. Does your submission pass tests?
  2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
  3. Have you checked your code using cargo clippy --all --all-features command?

This comment was marked as resolved.

@timvisee timvisee requested review from ffuugoo and removed request for agourlay March 20, 2025 08:10
@timvisee timvisee merged commit 133c8d7 into dev Mar 20, 2025
17 checks passed
@timvisee timvisee deleted the mutable-id-tracker-version-count-warning branch March 20, 2025 13:35
timvisee added a commit that referenced this pull request Mar 21, 2025
…ch (#6207)

* Add warning if mapping and version count mismatch, WAL should recover

* Make log messages more consistent and concrete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants