Distributed File Metadata Buckets for Scalable Data Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional file systems face scalability limitations due to centralized metadata management, leading to data loss in case of server failure and inability to scale beyond small clusters.

Innovation Solution

A distributed file system architecture that utilizes non-volatile memory (NVM) and metadata distribution across multiple servers, allowing for scalable metadata management and load balancing through penta-groups and distributed erasure coding, enabling high-performance parallel commits and independent bucket operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized metadata management is used, then file system control and data protection are improved, but scalability is limited and system complexity increases

Engineering Contradiction:
Improvedata protectionVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent divides the centralized metadata management into distributed metadata servers, each managing metadata for specific portions of the file system. This segmentation allows the system to scale by adding more metadata servers without overwhelming a single centralized controller, while maintaining data protection through replication across multiple servers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical metadata structure with metadata servers organized in tiers or dimensions, where metadata about metadata is stored separately. This dimensional approach to metadata organization enables better distribution of management responsibilities and improves scalability while maintaining control and protection capabilities.

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

2Reliability

If centralized metadata management is used, then data protection is improved, but system complexity increases

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

Solution Approach 1:

By segmenting metadata management across multiple independent servers, the patent reduces the complexity burden on any single system component. Each metadata server operates independently managing its portion of metadata, which simplifies individual server design while collectively providing robust data protection through distribution.

Inventive Principle:
Principle #1Segmentation

3Device complexity

If small cluster size is limited, then system simplicity is maintained, but scalability and performance are insufficient

Engineering Contradiction:
Improvesystem simplicityVSAvoidperformance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the file system into independent buckets that can be distributed across multiple servers. This allows the system to maintain simplicity through modular bucket management while achieving high performance by parallelizing operations across large clusters. Each bucket can be independently managed and scaled.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic metadata management where the system can adaptively distribute and reconfigure metadata across servers based on workload demands. This dynamic approach allows the system to maintain simplicity in operation while scaling performance capabilities as needed.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12591540B2Data migration in a distributive file system
Publication Date: 2026.03.31 WEKA IO LTD
  • US12591540B2 patent drawing
  • US12591540B2 patent drawing
  • US12591540B2 patent drawing

AI summary

A plurality of computing devices are communicatively coupled to each other via a network, and each of the plurality of computing devices is operably coupled to one or more of a plurality of storage devices. A plurality of failure resilient address spaces are distributed across the plurality of storage devices such that each of the plurality of failure resilient address spaces spans a plurality of the storage devices. The plurality of computing devices maintains metadata that maps each failure resilient address space to one of the plurality of computing devices. The metadata is grouped into buckets. Each bucket is stored in the backend of a computing device. Data may be migrated from an external file system to the plurality of storage devices using inode stubs to represent directories and files of the external file system. As the contents of the external file system are copied, the inode stubs are replaced with real inodes.