Dynamic Lock Management Hierarchy for Distributed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing lock management systems in distributed systems experience high lock access delays and performance issues due to a fixed number of lock management levels, which cannot be adjusted according to changing numbers of service execution nodes, system instances, and handling processes, leading to inefficient lock request handling.
Innovation Solution
A dynamic lock management system is configured for each service execution node based on the number of nodes, system instances, handling processes, and access delays, allocating multiple lock managers (node, local, and global) to manage lock requests efficiently, with a lock level context determining adjacent managers and handling lock requests sequentially until the global manager.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a fixed number of lock management levels is used in the lock management system, then the system structure is simple and easy to implement, but the lock access delay increases and system performance deteriorates when a large number of lock access requests occur
Solution Approach 1:
The patent applies dynamics by making the lock management system hierarchy adjustable rather than fixed. The system can dynamically add or remove intermediate lock managers based on the number of service execution nodes, transforming a static two-level structure into a flexible multi-level structure that adapts to system scale and performance requirements
Solution Approach 2:
The patent segments the lock management functionality into multiple hierarchical levels (global lock manager, intermediate lock managers, and node lock managers). This segmentation distributes the lock management workload across multiple levels, reducing the burden on any single manager and decreasing lock access delay when handling large numbers of requests
2Productivity
If the lock management system uses a multi-level hierarchy with intermediate lock managers, then the lock access delay is reduced and system performance is improved, but the system complexity increases
Solution Approach 1:
The patent implements universality by designing intermediate lock managers that can serve multiple functions: they act as both lower-level managers for node lock managers and upper-level managers for receiving lock requests. This multi-functionality reduces the need for completely separate management layers and helps control system complexity while maintaining performance benefits
3Ease of manufacture
If the number of lock management levels is determined during program development, then the configuration is simple and quick, but the system cannot adapt to changing numbers of service execution nodes, instances, and processes
Solution Approach 1:
The patent applies dynamics by enabling the lock management hierarchy to be dynamically adjusted during system operation rather than being fixed at development time. The system can automatically add or remove intermediate lock managers based on changes in the number of service execution nodes, instances, or processes, maintaining both ease of configuration and high adaptability
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Embodiments of the present invention disclose a lock management method and system, and a method and an apparatus for configuring a lock management system, which relate to the computer field, and can reduce a lock access delay and improve system running performance. A specific solution is as follows: A corresponding level of a lock management system is set for each service execution node according to the number of service execution nodes included in a distributed system, the number of system instances on all service execution nodes, the number of handling processes on all the service execution nodes, and a delay of access of each service execution node to a central control node of the distributed system; at least one lock manager is allocated to each service execution node separately according to the level, which is corresponding to each service execution node, of the lock management system; a lock level context is configured for each lock manager, where the lock level context is used to determine an adjacent lock manager of each lock manager. The present invention is applied to a lock management system in a distributed system.