Detachable Library Data Pointer Mapping in Distributed Clusters

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Archived content created with one content management system is difficult to retrieve and access using a different content management system due to compatibility issues and file identifier collisions.

Innovation Solution

Implementing a detachable library system with two layers of indirect addressing: library scope ID and cluster scope ID, which allows data files to be decoupled from the original database instance, avoiding file identifier collisions and enabling efficient attachment to new databases without modifying file pointers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If archived content is stored using a different content management system, then long term storage is achieved, but retrieval and access using a new content management system becomes difficult

Engineering Contradiction:

Improvestorage durationVSAvoidretrieval ease

Core Design Contradiction:

Duration of action of stationary objectVSEase of operation

Solution Approach 1:

The system segments the identifier space into two distinct layers: cluster-level identifiers (node scope IDs) and database-level identifiers (library scope IDs). This segmentation allows archived content to be detached from its original database instance while maintaining a mapping between the two identifier levels, enabling retrieval without direct pointer references to the original database.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that translates between node scope IDs (used in archived content) and library scope IDs (used by the new database system). This intermediary layer decouples the archived content from the original database instance, allowing retrieval through a new content management system without modifying the archived pointers.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Speed

If direct file pointers are used in archived content, then access speed is improved, but file identifier collisions occur when attaching to new databases

Engineering Contradiction:

Improveaccess speedVSAvoididentifier collision avoidance

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The system adds an additional dimension to the identifier system by introducing a second level of indirection. Instead of single-level direct pointers, the system uses a two-dimensional identifier space (node scope ID + library scope ID), which exponentially increases the available unique identifiers and eliminates collisions when attaching archived content to new databases.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The mapping mechanism acts as an intermediary that resolves the conflict between direct pointers and identifier uniqueness. The mapping table stores translations from node scope IDs (preserved in archived content) to library scope IDs (unique in the new database), allowing direct pointers to be maintained in archived files while avoiding collisions in the new system.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If file pointers are updated to accommodate new databases, then compatibility is improved, but modification complexity increases

Engineering Contradiction:

Improvedatabase compatibilityVSAvoidpointer modification complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-generating node scope IDs for archived content using a predictable algorithm based on the original database instance. This preliminary assignment of identifiers allows the archived content to be self-contained with valid pointers that can be later mapped to the new database system without requiring any modification to the archived files themselves.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The mapping mechanism serves as an intermediary that handles the complexity of pointer translation. Instead of modifying pointers in archived content, the mapping table absorbs the complexity by storing the translation rules, allowing the archived files to remain unchanged while achieving compatibility with new databases.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10599717B1System and method to represent data pointers in the distributed cluster environment

Publication Date: 2020.03.24 EMC IP HLDG CO LLC

AI summary

In general the technology includes obtaining a detachable library, where the detachable library includes data files each of which are associated with a library scope identifier (ID). The technology further includes reattaching the detachable library to a node server, assigning a node scope ID and a cluster scope ID to each of the data files in the detachable library, creating a mapping index using the node scope IDs, the cluster scope IDs, and the library scope IDs, where each of mapping index entry in the mapping index is associated with a type, and processing a request from a client using the mapping index, wherein the request includes a cluster scope ID.