Tag Replication in Global Scale Storage Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems face challenges in interoperability, replication, and migration of files with different layouts due to varying placements of tags in different file system versions, leading to inefficiencies in data management and storage.

Innovation Solution

A global scale system abstracts layout differences for placement hint tags, allowing seamless replication and migration between file systems with old and new layouts by storing tags in either inodes or extended attributes based on the file system version, and using a federated unified namespace server for transparent data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If file systems use different layouts for placement hint tags in different versions, then new features and improved data placement can be supported, but interoperability and replication between different file system versions become challenging

Engineering Contradiction:
Improvesupport for new file system featuresVSAvoidinteroperability between file system versions
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a metadata translation layer that acts as an intermediary between file systems with different tag layouts. This translation layer converts tags from new layouts to old layouts during replication operations, enabling seamless interoperability between different file system versions without requiring upgrades to all nodes simultaneously

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If tags are stored in different locations in different file system versions, then each version can optimize for its specific features, but replication and migration between versions become complex and error-prone

Engineering Contradiction:
Improveoptimization for specific file system featuresVSAvoidcomplexity of replication between versions
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent changes the parameter of tag storage location dynamically based on the file system version. The system automatically adjusts whether to store tags in inodes or extended attributes depending on the destination file system's layout requirements, simplifying replication by making the storage location a variable parameter rather than a fixed structural constraint

Inventive Principle:
Principle #35Parameter changes

3Stability of the object's composition

If all file system nodes are upgraded to support new tag layouts simultaneously, then consistent data placement can be achieved, but significant investment and disruption are required

Engineering Contradiction:
Improveconsistency of data placementVSAvoidupgrade effort and disruption
Core Design Contradiction:
Stability of the object's compositionVSEase of operation

Solution Approach 1:

The patent implements preliminary action by introducing the translation layer and layout abstraction mechanisms before universal adoption of new tag layouts is achieved. This allows the system to prepare for and gradually transition to new layouts while maintaining backward compatibility, enabling incremental adoption rather than requiring simultaneous upgrades across all nodes

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11886387B2Replication of tags in global scale systems
Publication Date: 2024.01.30 DELL PROD LP
  • US11886387B2 patent drawing
  • US11886387B2 patent drawing
  • US11886387B2 patent drawing

AI summary

Replication of tags in global scale systems is described. A source node creates a file and a grouping tag for the file. The source node stores the grouping tag in a location in metadata for the file. When preparing for replication, the source node retrieves the grouping tag from the location in the metadata. If the legacy location in the metadata includes any value which was stored after the most recent replication involving the file, and the size of the legacy location in the metadata was not changed after the most recent replication involving the file, the system adds the grouping tag to the legacy location in the metadata which includes any value which was stored after the most recent replication involving the file. The system sends the metadata, which includes the grouping tag and any value stored at the legacy location in the metadata, to a destination node.