Introduce data consistency checking and repair toolkit.#308
Draft
ibrarahmad wants to merge 2 commits intopgEdge:mainfrom
Draft
Introduce data consistency checking and repair toolkit.#308ibrarahmad wants to merge 2 commits intopgEdge:mainfrom
ibrarahmad wants to merge 2 commits intopgEdge:mainfrom
Conversation
added 2 commits
January 7, 2026 01:54
This commit introduces a comprehensive toolkit for data consistency checking and repair operations in Spock multi-master replication environments. The toolkit provides essential primitives for detecting data divergence between nodes, monitoring replication health, and generating precise SQL repair statements to restore consistency across the cluster. The toolkit delivers powerful building blocks for consistency workflows. It enables deep inspection of table metadata, precise comparison of row data between nodes, pinpoint identification of divergent columns, and intelligent generation of targeted repair SQL. Health monitoring capabilities assess subscription status and table integrity to identify replication issues before they propagate into widespread data inconsistencies. These production-ready functions form the foundation for building sophisticated repair workflows and operational tools. They handle edge cases gracefully, provide detailed error diagnostics, and integrate naturally into monitoring pipelines for mission-critical multi-master deployments.
- Implement UPSERT logic using INSERT ... ON CONFLICT DO UPDATE SET - Add Phase 3b for DELETE operations with p_delete_extra_rows parameter - Enhance crash scenario to test all three operation types - Update reporting with rows_inserted and rows_deleted statistics - Treat source node as authoritative source of truth
Member
|
Converted to a draft for now until we finalize similar work in ACE |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit introduces a comprehensive toolkit for data consistency checking and repair operations in Spock multi-master replication environments. The toolkit provides essential primitives for detecting data divergence between nodes, monitoring replication health, and generating precise SQL repair statements to restore consistency across the cluster.
The toolkit delivers powerful building blocks for consistency workflows. It enables deep inspection of table metadata, precise comparison of row data between nodes, pinpoint identification of divergent columns, and intelligent generation of targeted repair SQL. Health monitoring capabilities assess subscription status and table integrity to identify replication issues before they propagate into widespread data inconsistencies.
These production-ready functions form the foundation for building sophisticated repair workflows and operational tools. They handle edge cases gracefully, provide detailed error diagnostics, and integrate naturally into monitoring pipelines for mission-critical multi-master deployments.