Distributed Metadata Server USIV Allocation for Scalable File Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed file systems face challenges in generating unique identifiers for file data and managing them efficiently across multiple metadata servers, particularly in systems supporting video editing, archiving, and distribution, where reliable and ordered sequencing of identifiers is crucial.

Innovation Solution

The implementation of Unique Shared Incrementing Values (USIVs) as file identifiers, where each metadata server maintains a local bucket of USIVs and increments them non-overlappingly, allowing for decentralized management without central control, using a token mechanism to ensure reliable and ordered sequencing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized metadata server is used to manage file identifiers, then identifier uniqueness can be ensured, but system scalability and performance deteriorate due to single point of failure and bottleneck

Engineering Contradiction:
Improveidentifier uniquenessVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the centralized metadata server into multiple distributed metadata servers, each managing a portion of the file system metadata. This segmentation allows the system to scale horizontally while maintaining identifier uniqueness through coordinated management across servers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a naming authority as an intermediary that coordinates identifier allocation across multiple metadata servers. The naming authority assigns unique identifier ranges to each metadata server, ensuring global uniqueness without requiring a single centralized server.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple metadata servers are deployed to improve scalability, then system productivity increases, but managing unique identifiers across servers becomes complex and error-prone

Engineering Contradiction:
Improvesystem scalabilityVSAvoididentifier management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having the naming authority pre-assign unique identifier ranges to each metadata server before they begin operation. This preliminary allocation simplifies subsequent identifier management, as each server knows its authorized range and can independently generate identifiers within that range without complex coordination.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If identifier allocation is decentralized across metadata servers, then system reliability and scalability improve, but ensuring ordered sequencing of identifiers becomes difficult

Engineering Contradiction:
Improvesystem availabilityVSAvoididentifier sequencing precision
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

The patent applies local quality by allowing each metadata server to independently manage and sequence identifiers within its locally assigned range. This local autonomy ensures that each server can operate reliably without waiting for centralized coordination, while the overall system maintains ordered sequencing through the hierarchical structure of locally-managed ranges.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8478873B2Techniques for use of a system-unique identifier in an architecture having a file system utilizing distributed metadata servers
Publication Date: 2013.07.02 HARMONIC INC
  • US8478873B2 patent drawing
  • US8478873B2 patent drawing
  • US8478873B2 patent drawing

AI summary

Use and generation of an identifier. An indication of a value to be used to generate system-unique identifiers is received. The indication and an associated count value are stored in a metadata server interconnected with one or more remote metadata servers. A modified value to be used to generate system-unique identifiers generated based, at least in part, on the indication and the associated count value is transmitted to a remote metadata server.