Metadata Server Table Indexing for Data Durability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed data storage systems face challenges with large metadata tables due to the need for durability and recovery, leading to congestion and sub-optimal performance, especially in cloud computing environments where metadata tables are impractical to transmit and suffer from poor durability and distribution among servers.

Innovation Solution

A metadata server generates a metadata table that associates each possible pair or combination of servers with indices, ensuring all servers participate in recovery and providing additional servers for data durability, or uses rules and parameters to enable clients to identify servers storing data items, allowing for efficient data distribution and recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single metadata server maintains a large metadata table to ensure data durability and identify multiple server replicas, then data durability is improved, but system congestion increases and performance deteriorates

Engineering Contradiction:
Improvedata durabilityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments the centralized metadata server functionality by distributing metadata table copies to multiple cache servers. Each cache server maintains a portion of the metadata table, eliminating the single point of congestion while preserving data durability through replicated metadata availability across multiple servers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Cache servers act as intermediaries between clients and the metadata table. Instead of clients directly querying a single metadata server, requests are routed through cache servers that hold local copies of metadata, reducing congestion on the primary metadata server while maintaining system reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the metadata table size is increased to identify multiple server replicas for each data item, then data durability is improved, but the metadata table becomes impractical to transmit to clients

Engineering Contradiction:
Improvedata durabilityVSAvoidmetadata table transmission complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of transmitting the entire large metadata table to each client, the system provides clients with local metadata cache files containing only the metadata relevant to their specific data access patterns. This reduces transmission complexity while maintaining data durability through selective metadata distribution.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system extracts and separates metadata from the main metadata table, providing clients with standalone metadata cache files that contain only the necessary mapping information for their data access needs, rather than requiring the complete metadata table.

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If servers are assigned to data items in a naïve manner, then device complexity is reduced, but data durability and recovery performance deteriorate

Engineering Contradiction:
Improveserver assignment complexityVSAvoiddata durability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system performs preliminary server pairing assignments before data storage operations. By pre-establishing server pairs and their corresponding metadata table indices, the system ensures that durable server combinations are identified in advance, improving data durability without adding operational complexity during data access.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically generates server pairings based on current server availability and performance characteristics. Rather than using static naïve assignments, the metadata server can adapt server pairings to changing system conditions, optimizing both data durability and recovery performance while maintaining manageable complexity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9454441B2Data layout for recovery and durability
Publication Date: 2016.09.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9454441B2 patent drawing
  • US9454441B2 patent drawing
  • US9454441B2 patent drawing

AI summary

A Metadata server described herein is configured to generate a metadata table optimized for data durability and recovery. In generating the metadata table, the metadata server associates each possible combination of servers with one of the indices of the table, thereby ensuring that each server participates in recovery in the event of a server failure. In addition, the metadata server may also associate one or more additional servers with each index to provide added data durability. Upon generating the metadata table, the metadata server provides the metadata table to clients or servers. Alternatively, the metadata server may provide rules and parameters to clients to enable those clients to identify servers storing data items. The clients may use these parameters and an index as inputs to the rules to determine the identities of servers storing or designated to store data items corresponding to the index.