Parallel File System Caching for Multi-Region Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized file systems face challenges in serving a large number of client devices across different geographical regions due to slow network connections and network congestion, leading to longer access times and computing bottlenecks.

Innovation Solution

A multi-cloud, multi-region parallel file system cluster service with caching between file system storage nodes, where data is pulled and stored in parallel across multiple servers to provide efficient data access and reduce latency, utilizing a loosely coupled global namespace and policy-driven data orchestration for synchronization and replication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data is stored in a centralized file system, then data access is simplified, but network congestion and computing bottlenecks occur when serving large numbers of client devices

Engineering Contradiction:
Improvedata access simplicityVSAvoiddata access speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The centralized file system is segmented into multiple distributed file system storage nodes that can independently serve client devices. Each node maintains a portion of the data and can handle requests autonomously, eliminating the single-point bottleneck while preserving unified access through the distributed namespace architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from a single-dimensional centralized storage model to a multi-dimensional distributed architecture where data exists across multiple geographical locations and storage nodes. This dimensional expansion allows simultaneous access from multiple points, reducing network congestion while maintaining data unity through replication and synchronization mechanisms.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Stability of the object's composition

If data is stored in a centralized location, then data consistency is maintained, but access times increase due to geographical distance and network latency

Engineering Contradiction:
Improvedata consistencyVSAvoiddata access time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

Data is pre-replicated to multiple geographically distributed storage nodes before client requests arrive. This preliminary distribution of data copies ensures that when access requests occur, clients can retrieve data from the nearest available node, significantly reducing access time while consistency is maintained through synchronization protocols.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and maintains multiple copies of data across different storage nodes and geographical regions. These copies enable local access without compromising data integrity, as the distributed namespace and synchronization mechanisms ensure all copies remain consistent with the master data.

Inventive Principle:
Principle #26Copying

3Productivity

If data is replicated across multiple regions, then access speed improves, but synchronization complexity increases

Engineering Contradiction:
Improvedata access speedVSAvoidsynchronization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The distributed file system implements feedback mechanisms where storage nodes continuously report their data state and synchronization status to a coordination service. This feedback loop enables automatic detection and resolution of synchronization issues, maintaining data consistency across regions without requiring complex manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Storage nodes autonomously manage their own data synchronization by implementing local copy-on-write operations and self-healing mechanisms. When data changes occur, the system automatically propagates updates to relevant nodes based on replication policies, reducing the need for complex centralized coordination while maintaining consistency.

Inventive Principle:
Principle #25Self-service

4Productivity

If data is cached at multiple storage nodes, then network congestion is reduced, but data placement optimization becomes more complex

Engineering Contradiction:
Improvenetwork efficiencyVSAvoiddata placement complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Storage nodes autonomously determine optimal data placement by analyzing local access patterns and network conditions. Each node independently decides which data to cache locally based on observed demand, eliminating the need for complex centralized placement algorithms while improving network efficiency through localized caching decisions.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces complex mechanical data placement algorithms with intelligent software-based policies that automatically adapt to changing access patterns. These software policies use heuristics and machine learning to optimize data placement decisions, reducing computational complexity while maintaining high network efficiency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11520742B2Data mesh parallel file system caching
Publication Date: 2022.12.06 CLOUDBRINK INC
  • US11520742B2 patent drawing
  • US11520742B2 patent drawing
  • US11520742B2 patent drawing

AI summary

Embodiments relate to providing a multi-cloud, multi-region, parallel file system cluster service with caching between file system storage nodes. In some embodiments, a first file system storage node of a file system storage cluster receives a request from a client device to access data of a first file system. In response to the request to access the data, a plurality of servers of the first file system storage node pulls, in parallel, the data and nearby data of the data from a second file system storage node of the file system storage cluster. The plurality of servers stores the data and nearby data in the first file system, and provide the data and nearby data to the client device.