Distributed Filesystem Encryption and Metadata Scaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional filesystems face scalability issues due to limited metadata server numbers, leading to inefficiencies in data storage and retrieval, especially in large-scale distributed systems.

Innovation Solution

The proposed solution involves a distributed filesystem architecture that scales by spreading metadata functionality across many servers, using non-volatile memory (NVM) for storage, and employing distributed erasure coding to ensure high performance and fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional centralized metadata servers are used, then data storage and retrieval can be managed, but scalability is limited and performance degrades in large-scale distributed systems

Engineering Contradiction:
Improvedata storage and retrieval efficiencyVSAvoidmetadata server architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the centralized metadata server into multiple distributed metadata servers across the network. Each metadata server manages a portion of the filesystem metadata, allowing the system to scale horizontally. This segmentation resolves the contradiction by distributing the load across multiple servers, maintaining efficiency while reducing the complexity burden on any single server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-dimension centralized architecture to a multi-dimensional distributed architecture. By adding the spatial dimension of distribution across multiple servers and the hierarchical dimension of metadata organization, the system achieves better scalability and performance without increasing individual server complexity.

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

2Adaptability or versatility

If the number of metadata servers is increased to improve scalability, then more nodes can be supported, but system complexity and coordination overhead increase

Engineering Contradiction:
Improvescalability to thousands of nodesVSAvoiddistributed metadata server coordination
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universal metadata server components that can handle multiple types of operations (create, read, update, delete, list) and serve multiple clients simultaneously. This multi-functionality allows the same metadata server architecture to scale from small to large deployments without requiring different coordination mechanisms, thus improving adaptability while controlling complexity.

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

Solution Approach 2:

The patent changes key parameters of the metadata server system, including the number of servers, the distribution of metadata partitions, and the replication factors. By dynamically adjusting these parameters based on system scale, the architecture can adapt to support from a few to thousands of nodes without fundamental redesign, resolving the scalability-complexity contradiction.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If data is encrypted at rest and in transit, then security is improved, but performance and processing time may be affected

Engineering Contradiction:
Improvedata security through encryptionVSAvoiddata access performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary encryption to data before it is written to storage (encryption at rest) and before it is transmitted over the network (encryption in transit). This preliminary action ensures security is built-in without affecting read performance, as encrypted data can be stored and transmitted efficiently, and decryption only occurs when absolutely necessary for data access.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses cryptographic copying where the original data remains encrypted and an authenticated copy is created through decryption only when needed. This approach maintains security while enabling performance optimization, as the system can work with encrypted data copies for most operations and only decrypt when absolutely necessary.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250181750A1Encryption for a distributed filesystem
Publication Date: 2025.06.05 WEKA IO LTD
  • US20250181750A1 patent drawing
  • US20250181750A1 patent drawing
  • US20250181750A1 patent drawing

AI summary

A computing device comprising a frontend and a backend is operably coupled to a plurality of storage devices. The backend comprises a plurality of buckets. Each bucket is operable to build a failure-protected stipe that spans two or more of the plurality of the storage devices. The frontend is operable to encrypt data as it enters the plurality of storage devices and decrypt data as it leaves the plurality of storage devices.