Distributed File System Access Coordination via Intermediary Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale computer systems with multiple independent processing nodes, fast access to files is hindered, making it difficult to efficiently manage and store digitized data such as images and videos.

Innovation Solution

A distributed file system architecture is implemented, comprising I/O nodes and compute nodes communicably coupled through an interconnect, with a distribution manager and file manager that facilitate file access by delegating responsibility for files or file ranges to subsets of compute nodes, using a message port system for communication and shared memory for data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a distributed file system architecture is implemented with multiple independent processing nodes, then scalability and data management capability are improved, but fast access to files from particular processing nodes deteriorates

Engineering Contradiction:
ImprovescalabilityVSAvoidfile access speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent introduces a file access coordinator as an intermediary component that receives file access requests from processing nodes, determines the optimal location of file data, and directs access operations. This mediator resolves the contradiction by centralizing access coordination while maintaining distributed storage, thereby preserving fast access speeds despite the distributed architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-caching frequently accessed file data in local memory of processing nodes and pre-establishing data placement mappings. This advance preparation ensures that when access requests arrive, the system can quickly serve data without traversing the entire distributed network, thus maintaining high access speeds in a scalable architecture.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If file data is distributed across multiple storage locations, then storage capacity and scalability are improved, but access time and retrieval efficiency worsen

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent segments the file system into distinct functional components: metadata servers that track data locations, distributed storage nodes that hold file segments, and cache layers at processing nodes. This segmentation allows the system to maintain large distributed storage capacity while reducing access time by directing requests to the correct segmented component that holds the required data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements local quality by caching frequently accessed file data and metadata in the local memory of processing nodes rather than relying solely on remote distributed storage. This creates different quality levels of data availability locally versus remotely, with hot data having fast local access and cold data residing in distributed storage, thereby reducing overall access time while maintaining scalability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7933875B2File system with distributed components
Publication Date: 2011.04.26 ORACLE AMERICAN INC
  • US7933875B2 patent drawing
  • US7933875B2 patent drawing
  • US7933875B2 patent drawing

AI summary

A distributed file system is disclosed which may include one or more input/output (I/O) nodes and one or more compute nodes. The I/O nodes and the compute nodes may be communicably coupled through an interconnect. Each compute node may include applications to perform specific functions and perform I/O functions through libraries and file system call handlers. The file system call handlers may be capable of providing application programming interfaces (APIs) to facilitate communication between the plurality of I/O nodes and the applications. The file system call handlers may use a message port system to communicate with other compute nodes.