Metadata Server File-Range Locking for Distributed Write Concurrency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional distributed file systems face inefficiencies and poor flexibility in managing file locks due to cumbersome lock range release and allocation processes, leading to low performance and poor concurrency in handling multiple client access to shared resources.

Innovation Solution

A metadata server-based method that allows flexible locking of file ranges by managing lock requests and versions, ensuring data consistency and reliability through version tokens and lease terms, enabling clients to actively request and release locks to avoid long-term locking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server allocates file ranges and manages lock range release and allocation, then data consistency is ensured, but the process becomes cumbersome and performance deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidlocking efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the file into multiple ranges and allows independent locking of each range. Instead of locking the entire file, clients can lock only the specific ranges they need to access, enabling fine-grained control and reducing lock contention. This segmentation resolves the contradiction by maintaining data consistency through range-level locking while improving performance by reducing the scope of locks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic lock range allocation where the server adjusts and allocates lock ranges based on actual client needs and current system state. The lock ranges are not fixed but can be dynamically modified, expanded, or contracted according to access patterns and availability, making the locking mechanism more adaptive and efficient.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the server manages lock range allocation centrally, then coordination between clients is achieved, but system complexity increases and flexibility decreases

Engineering Contradiction:
Improvecoordination reliabilityVSAvoidlock management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

By segmenting the file into manageable ranges and allowing clients to independently manage locks on specific ranges, the system reduces the complexity of centralized lock management. Each range can be locked independently, simplifying the coordination logic compared to managing entire file locks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different locking policies and mechanisms for different file ranges based on their access patterns and requirements. Each range can have its own lock state and management characteristics, enabling localized optimization without affecting the entire file system.

Inventive Principle:
Principle #3Local quality

3Reliability

If clients lock entire files for write operations, then data consistency is maintained, but concurrency is reduced and performance suffers

Engineering Contradiction:
Improvedata consistencyVSAvoidwrite concurrency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the file into multiple lockable ranges, allowing multiple clients to simultaneously hold locks on different ranges. This enables concurrent write operations on different portions of the file, significantly improving write concurrency while maintaining data consistency through proper lock management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of requiring clients to lock the entire file, the patent allows clients to lock only the partial ranges they need for their write operations. This partial locking approach reduces lock contention and enables higher concurrency while still ensuring data consistency for the locked portions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12436923B2Distributed data access control and data storage method, metadata server, and client
Publication Date: 2025.10.07 HUAWEI TECH CO LTD
  • US12436923B2 patent drawing
  • US12436923B2 patent drawing
  • US12436923B2 patent drawing

AI summary

A data storage method includes a first client sending a first lock request for locking a first data range of a first file to a metadata server. The metadata server receives the first lock request from the first client. When the first data range of the first file is not locked, the metadata server locks the first data range of the first file and sends a first lock response to the first client to indicate that the first data range of the first file is locked by the first client.