Multi-Node File System Cache for Disconnected Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cluster file systems face challenges in maintaining consistent and efficient file data sharing across wide-area networks, particularly in scenarios with intermittent or long-term network outages, as they struggle to support disconnected file operations and synchronize data updates effectively.

Innovation Solution

A scalable multi-node file system cache is implemented, allowing for caching of file data on demand from a remote cluster file system, enabling file operations to continue during disconnection and synchronizing with the remote system upon reconnection, using a caching layer that supports data and metadata updates even during network outages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a remote cluster file system is accessed over a wide-area network, then file data sharing capacity and bandwidth can be scaled, but network outages and latency prevent continuous file operations

Engineering Contradiction:
Improvefile data sharing capacityVSAvoidcontinuous operation during network outages
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements a local cache that pre-loads and stores file data blocks before they are needed, allowing the system to operate continuously during network outages. The cache maintains a local copy of file data that can be accessed without network connectivity, and synchronization mechanisms ensure data consistency when the network is restored.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The local cache acts as an intermediary between the client and the remote cluster file system. It buffers file operations locally, allowing continuous file access during network outages, and then synchronizes with the remote system when connectivity is restored, resolving the contradiction between scaled remote access and continuous operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If file data is cached locally to enable disconnected operations, then continuous operation is maintained, but data consistency with the remote system becomes challenging

Engineering Contradiction:
Improvecontinuous file operations during disconnectionVSAvoiddata consistency between cache and remote system
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent implements synchronization mechanisms that provide feedback between the local cache and remote cluster file system. Change tracking monitors modifications in the cache, and upon reconnection, the system detects and resolves conflicts by comparing timestamps and file versions, ensuring data consistency while maintaining continuous operation capability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The cache system dynamically adjusts its behavior based on network connectivity status. During disconnection, it operates autonomously with full write capability. Upon reconnection, it transitions to synchronization mode where it detects changes, resolves conflicts, and updates the remote system, thereby maintaining both continuous operation and data consistency.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If all file operations are supported at the cache during disconnection, then ease of operation is improved, but complexity of synchronizing upon reconnection increases

Engineering Contradiction:
Improvefile operation availability during disconnectionVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the file system into a local cache component and a remote cluster file system component. The cache handles all file operations independently during disconnection, maintaining ease of operation. Upon reconnection, the synchronization mechanism is activated as a separate process that detects changes and resolves conflicts, managing complexity by isolating it from the core file operation path.

Inventive Principle:
Principle #1Segmentation

4Productivity

If a local cache is implemented to mask network latency, then performance is improved, but storage requirements and cache management complexity increase

Engineering Contradiction:
Improvefile system performanceVSAvoidcache management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The cache implementation uses self-managing mechanisms including automatic cache invalidation, hierarchical cache management, and intelligent prefetching algorithms. These self-service features improve file system performance by masking network latency while minimizing the operational complexity for users, as the cache manages itself without requiring manual intervention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8473582B2Disconnected file operations in a scalable multi-node file system cache for a remote cluster file system
Publication Date: 2013.06.25 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8473582B2 patent drawing
  • US8473582B2 patent drawing
  • US8473582B2 patent drawing

AI summary

Facilitating access to data in a network, is provided. One implementation involves maintaining a scalable multi-node file system cache in a local cluster file system, and caching file data in a cache by fetching file data on demand from a remote cluster file system into the local cached file system over the network. The local file data corresponds to file data in the remote cluster file system. Upon disconnection from the remote cluster file system, all file operations are supported at the cache. Then, upon reconnection to the remote cluster file system over the network, the remote cluster file system is synchronized with the information cached in the cache during the disconnection even in the presence of failures.