Index Page Split Atomicity in Multi-Master Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-master databases, index page splits are prone to inconsistencies and conflicts during concurrent writes, often requiring transactional support or locking mechanisms, which introduce performance overhead and are not universally applicable.
Innovation Solution
A method and apparatus for performing index page splits using a page registry table to track conflicts and propagate abort operations, ensuring atomicity by treating updates as a single operation that either succeeds or fails, reducing reliance on locking and transactional support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If transactional support or locking mechanisms are used to ensure atomic index page splits, then consistency and reliability are improved, but performance overhead and system complexity increase
Solution Approach 1:
The patent extracts the conflict detection and resolution logic from the traditional transactional/locking mechanism. Instead of relying on external transaction support or locking, the system uses a page registry table to track which pages are being split and propagates abort operations through the index tree hierarchy, thereby achieving atomicity without the overhead of transactions or locks.
Solution Approach 2:
The patent introduces a page registry table as an intermediary data structure to mediate the index page split operation. The registry table tracks the state of pages undergoing splits and enables coordinated abort propagation across multiple levels of the index tree, replacing the need for transactional support or locking mechanisms.
2Reliability
If transactional support or locking mechanisms are used to ensure atomic index page splits, then consistency is improved, but device complexity increases
Solution Approach 1:
The patent removes the dependency on external transactional support or locking mechanisms by extracting the essential functionality into a dedicated page registry table and abort propagation mechanism. This simplifies the overall system architecture by eliminating the need for complex transaction management infrastructure while maintaining atomicity guarantees.
Solution Approach 2:
The page registry table serves as a simple intermediary that coordinates the split operation across multiple pages and levels without requiring complex transaction protocols or locking hierarchies. This intermediary approach reduces system complexity by providing a straightforward mechanism for tracking and coordinating split operations.
3Reliability
If traditional locking mechanisms are used during index page splits, then consistency across concurrent writes is improved, but performance overhead increases
Solution Approach 1:
The patent extracts the conflict detection functionality from locking mechanisms and implements it through the page registry table. By tracking pages in the registry and propagating abort operations, the system achieves concurrent write consistency without the time overhead of acquiring and holding locks during split operations.
Solution Approach 2:
The system uses self-service abort propagation where the page registry automatically tracks and coordinates abort operations across the index tree hierarchy. This eliminates the need for external locking coordination, allowing concurrent writes to proceed without locking overhead while maintaining consistency through automatic abort propagation when conflicts are detected.
Data Source
AI summary
Methods and apparatus are described for splitting a page (or node) in an index tree database index for a multi-master database. The methods include creating a first split page of a first page. The first page belongs to a first set of pages and comprises a hinge page. The hinge page also belongs to a second set of pages. Updating the first set of pages may cause the hinge page itself to split, creating a split of the hinge page. The second set of pages is updated in response to creating the split of the hinge page. Described are techniques whereby the updates to the first and second sets of pages are atomic, that is, they all succeed or they all fail, which may realize any of several benefits.