Module consistency

Source

Structs§

ShardState 🔒
Parts of a shard’s state that we read to determine if it’s a tombstone.

Enums§

Level
Level of consistency checks we should enable on a testdrive run.

Functions§

check_catalog_state 🔒
Checks that the in-memory catalog matches what we have persisted on disk.
check_coordinator 🔒
Asks the Coordinator to run it’s own internal consistency checks.
check_shard_tombstone 🔒
Checks if the provided shard_id is a tombstone, returning an error if it’s not.
check_statement_logging 🔒
This currently checks only whether the statement log reports all statements to be in a finished state. (We used to have an assertion for roughly this in ExecuteContextExtra’s Drop, but that had to be removed due to https://github.com/MaterializeInc/database-issues/issues/7304)
run_check_shard_tombstone
Checks if a shard in Persist has been tombstoned.
run_consistency_checks
Runs consistency checks against multiple parts of Materialize to make sure we haven’t violated our invariants or leaked resources.
skip_consistency_checks
Skips consistency checks for the current file.