Distributed Lock-State Management for Dispersed Database Datasets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face limitations in processing speed due to hardware constraints, data storage methods, and restricted co-processing options, leading to inefficiencies in data management and query execution.
Innovation Solution
A database system architecture that employs parallelized data input, storage, and query processing across multiple computing devices and nodes, utilizing a lock management protocol to manage lock state data and optimize query execution plans, enabling efficient storage and retrieval of dispersed data sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in a centralized database system, then data consistency is maintained, but processing speed and query execution efficiency deteriorate due to hardware constraints and sequential access limitations
Solution Approach 1:
The patent segments the centralized database into multiple dispersed data sets stored across different computing devices. Each data set is independently managed with local lock state tracking, enabling parallel processing while maintaining consistency through a coordination layer that manages lock state data across the distributed system.
2Reliability
If traditional lock management is used in centralized databases, then data integrity is ensured, but query execution time increases due to sequential lock acquisition and centralized coordination overhead
Solution Approach 1:
The patent introduces a new dimension for lock management by maintaining lock state data locally at each computing device rather than centralizing it. This distributed lock state tracking enables concurrent query execution across multiple devices while preserving data integrity through coordinated lock state updates managed by the database system.
3Productivity
If data is dispersedly stored across multiple computing devices, then processing parallelism and speed are improved, but lock state management complexity and coordination overhead increase
Solution Approach 1:
The patent introduces lock state data as an intermediary mechanism that mediates between dispersed data storage and consistency requirements. Each computing device maintains local lock state information for its data sets, eliminating the need for complex centralized coordination while enabling parallel processing through independent local lock management.
4Productivity
If hardware resources are increased to improve database processing speed, then processing capacity increases, but system cost and hardware dependency increase
Solution Approach 1:
The patent changes the architectural parameter from centralized to dispersed data storage and management. By distributing data sets across multiple computing devices and implementing local lock state tracking, the system achieves parallel processing capabilities that scale with available hardware resources without creating single-point bottlenecks, thereby improving processing capacity while reducing hardware dependency on any single device.
Data Source
AI summary
A method includes obtaining, by a lock state management module of a leader computing node of a plurality of computing nodes, a first lock request from a first client. The first lock request corresponds to a first data access request of a first dataset. The first data set is dispersedly stored across a set of computing nodes of the plurality of computing nodes. The method further includes identifying a first pending lock request queue of a plurality of pending lock request queues of shared lock state data based on first lock metadata of the first lock request. The shared lock state data is shared by the leader computing node with other computing nodes of the plurality of computing nodes. The method further includes adding the first lock request to the first pending lock request queue in accordance with a prioritization ordering, determining to grant the first lock request based on a set of grant conditions to produce a granted first lock request of a first set of granted lock requests of the shared lock state data, and removing the first granted lock request from the first set of granted lock requests upon a removal indication.