Common Log Node for Shared Database Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database systems face conflicts and processing delays due to communication issues between processing nodes and storage nodes, particularly when multiple nodes attempt to write to the same database portion concurrently, leading to inefficiencies and operational challenges.
Innovation Solution
A common log node is introduced to coordinate transactions between processing nodes and storage nodes, validating requests, detecting conflicts, and managing locks to ensure exclusive access, thereby preventing conflicts and minimizing delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple processing nodes access the database concurrently, then system productivity increases, but conflicts occur leading to processing delays and reduced reliability
Solution Approach 1:
A common log node is introduced as an intermediary between processing nodes and storage nodes. The common log node receives modify operations from processing nodes, validates version numbers to detect conflicts, and coordinates lock management. This mediator prevents direct conflicts by ensuring only one processing node can modify a page at a time while allowing multiple nodes to read simultaneously, thus maintaining data consistency while supporting concurrent access
Solution Approach 2:
The system performs preliminary validation of version numbers before executing modify operations. When a processing node requests to modify a page, the common log node checks if the requested base version number matches the current latest validated version number. This preliminary check prevents conflicting writes by detecting version mismatches before they occur, ensuring data consistency is maintained while allowing concurrent read operations
2Reliability
If locks are implemented to prevent conflicts, then data integrity is improved, but processing delays increase due to exclusive access requirements
Solution Approach 1:
Locks are applied selectively at the page level rather than at the database level. The common log node grants exclusive locks only to specific pages that are being modified, while other pages remain accessible to multiple processing nodes. This localized locking approach minimizes the impact on overall system throughput by allowing concurrent access to different portions of the database while maintaining data integrity for the specific page being modified
3Measurement precision
If version validation is performed to detect conflicts, then measurement precision of conflict detection is improved, but device complexity increases
Solution Approach 1:
The system uses version numbers as simplified copies of the actual page state for conflict detection purposes. Instead of comparing entire page contents or maintaining complex conflict detection logic, the common log node validates modify operations by comparing version numbers (base version number vs. latest validated version number). This copying approach maintains high conflict detection accuracy while significantly reducing system complexity and validation overhead
Data Source
AI summary
Methods and systems are described for managing a shared database. One or more processing nodes may access a shared database. A common log node may manage the shared database. The common log node may validate database operations requested by the one or more processing nodes. During validation, the common log node may detect conflicts that occur between database operations requested by the one or more processing nodes.