Distributed Metadata Architecture for Cloud Storage Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cloud storage systems lack scalability for small files, have limited metadata capacity, and do not provide end-to-end data integrity and inline distributed deduplication, which restricts their deployment for applications requiring small files and high metadata handling.

Innovation Solution

The system distributes metadata between object-tracking and chunk-tracking metadata, using a federated file system for object metadata and a distributed database for chunk metadata, optimized with solid state drives and tailored storage requirements, enabling scalable metadata processing and inline deduplication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If conventional cloud storage systems use a centralized metadata server, then system simplicity is maintained, but metadata capacity and scalability are limited

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

Solution Approach 1:

The patent segments metadata into two distinct types: object-tracking metadata stored in a federated file system and chunk-tracking metadata stored in a distributed database. This segmentation allows each metadata type to be managed independently with optimized storage mechanisms, dramatically increasing overall metadata capacity without creating a single point of failure or bottleneck

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If cloud storage systems support a large number of clients, then service coverage is improved, but metadata handling scalability deteriorates

Engineering Contradiction:
Improveclient scalabilityVSAvoidmetadata handling scalability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

By dividing metadata responsibilities between object-tracking (federated file system) and chunk-tracking (distributed database), the system can handle metadata operations in parallel across multiple nodes, enabling both increased client capacity and maintained metadata handling scalability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a two-dimensional metadata architecture where object metadata and chunk metadata operate in separate dimensions with different storage optimizations. This dimensional separation allows the system to scale clients in one dimension while maintaining efficient metadata handling in the other dimension through specialized storage paths

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

3Reliability

If cloud storage systems use traditional file systems, then ease of operation is maintained, but end-to-end data integrity and inline distributed deduplication are not provided

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer between the federated file system and chunk servers that implements end-to-end data integrity checking and inline distributed deduplication. This intermediary handles cryptographic verification and deduplication operations without requiring fundamental changes to the underlying file system architecture, maintaining operational simplicity while adding reliability features

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8533231B2Cloud storage system with distributed metadata
Publication Date: 2013.09.10 NEXENTA BY DDN INC
  • US8533231B2 patent drawing
  • US8533231B2 patent drawing
  • US8533231B2 patent drawing

AI summary

A method and system is disclosed for providing a cloud storage system supporting existing APIs and protocols. The method of storing cloud storage system (CSS) object metadata separates object metadata that describes each CSS object as a collection of named chunks with chunk locations specified as a separate part of the metadata. Chunks are identified using globally unique permanent identifiers that are never re-used to identify different chunk payload. While avoiding the bottleneck of a single metadata server, the disclosed system provides ordering guarantees to clients such as guaranteeing access to the most recent version of an object. The disclosed system also provides end-to-end data integrity protection, inline data deduplication, configurable replication, hierarchical storage management and location-aware optimization of chunk storage.