Object File System Segmentation for Distributed Storage Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file systems provide limited access and management capabilities for large volumes of data, particularly in web applications, and lack efficient mechanisms for handling data redundancy and storage node failures.

Innovation Solution

An object file system that supports basic commands like write, read, and delete, with additional commands for reserving space and reserve write, utilizing an object access system to communicate with storage nodes, and a database for metadata management, along with a tuning server for dynamic adjustments and redundancy handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a distributed hierarchical file system is used to store large numbers of objects, then storage capacity and data management capability are improved, but system complexity and difficulty of detecting and measuring system state increase

Engineering Contradiction:
Improvestorage capacityVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments the file system into distinct functional components: storage nodes for data storage, a metadata server for managing object metadata, and a tuning server for optimizing system performance. This segmentation allows each component to be independently managed and scaled, reducing overall system complexity while maintaining large storage capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a metadata server as an intermediary between clients and storage nodes. This mediator handles metadata operations centrally, simplifying the complexity of tracking object locations and attributes across distributed storage nodes, while enabling the system to scale storage capacity independently.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If basic file system commands are implemented, then ease of operation is improved, but functionality and adaptability are limited

Engineering Contradiction:
Improveease of operationVSAvoidfunctionality
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal object interface that supports multiple operations including read, write, delete, and specialized operations like reserve and reserve write. This multi-functional interface maintains ease of operation through consistent command structures while providing adaptability for various data management scenarios including web applications and backup systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces dynamic space reservation capabilities where objects can reserve storage space in advance and perform reserved writes. This dynamic functionality allows the system to adapt to varying storage requirements while maintaining simple operation through standardized commands, enabling both ease of operation and versatility.

Inventive Principle:
Principle #15Dynamics

3Reliability

If data is distributed across multiple storage nodes, then storage capacity and reliability are improved, but difficulty of detecting and measuring system state increases

Engineering Contradiction:
ImprovereliabilityVSAvoidsystem state monitoring
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a tuning server that continuously monitors the state of storage nodes and metadata server, collecting feedback information about system performance and health. This feedback mechanism enables automatic detection of system state changes and facilitates adaptive optimization, making distributed system monitoring manageable despite the complexity of multiple nodes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The metadata server acts as an intermediary that centralizes tracking of object locations across distributed storage nodes. This mediator simplifies the detection and measurement of system state by providing a single point of query for object metadata, reducing the complexity of monitoring distributed data despite improved reliability through distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If automatic adaptation to storage node failures is implemented, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary actions for failure recovery by maintaining metadata about object locations and using a tuning server to pre-establish recovery procedures. When storage node failures occur, the system can automatically adapt by querying the metadata server for alternative locations and redistributing data, achieving fault tolerance through pre-planned recovery mechanisms rather than complex real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9189494B2Object file system
Publication Date: 2015.11.17 DATADIRECT NETWORKS INC
  • US9189494B2 patent drawing
  • US9189494B2 patent drawing
  • US9189494B2 patent drawing

AI summary

An object based file system for storing and accessing objects is disclosed. The file system may be implemented as a method in hardware, firmware, software, or a combination thereof. The method may include receiving from an application program an object write request. A selected storage node on which to store the object may be selected, including identifying a least busy storage node and/or a least full storage node. The object and the object write request may be sent to the selected storage node. A write success message may be received from the selected storage node. The successful writing of the object may be reported to the application program.