Shadow Root Data Replication in P2P Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern P2P storage systems face challenges in ensuring the availability and reliability of critical data due to the failure or disconnection of dedicated control entities responsible for replicating and maintaining backup copies of important objects across nodes.

Innovation Solution

The system employs a method of generating a derived globally unique identifier (GUID) for an object, creating a shadow root to store and replicate copies, ensuring that critical data remains accessible even if the primary root node fails or becomes disconnected by automatically assigning new root nodes and creating additional shadow roots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dedicated control entity is used to ensure replication and availability of critical data, then data reliability is improved, but system complexity increases and single point of failure risk increases

Engineering Contradiction:
Improvedata availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables nodes to automatically detect data loss conditions and initiate replication without requiring a dedicated control entity. Each node monitors data availability and autonomously performs replication operations, eliminating the single point of failure while maintaining reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-establishes replication mechanisms and automatic detection protocols before failures occur. When a node detects data loss, the pre-configured automatic replication process is immediately activated, ensuring continuous availability without manual intervention or complex control systems.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a dedicated control entity periodically checks replica existence, then data reliability is improved, but system complexity increases

Engineering Contradiction:
Improvedata availabilityVSAvoidcontrol mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Nodes autonomously monitor their own data availability and trigger replication when needed, eliminating the need for a dedicated control entity to periodically check replica existence. Each node serves its own reliability needs through self-detection and self-initiation of replication.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements distributed feedback mechanisms where nodes continuously monitor data availability and automatically adjust replication behavior. This feedback loop operates at the node level rather than requiring centralized control, reducing system complexity while maintaining reliability.

Inventive Principle:
Principle #23Feedback

3Reliability

If multiple copies of critical data are stored on different nodes, then data reliability is improved, but storage requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system automatically determines and implements the minimum necessary replication based on detected failure conditions rather than requiring predetermined fixed replication ratios. This dynamic approach ensures sufficient redundancy only when and where needed, optimizing storage usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The replication strategy dynamically adjusts based on real-time system conditions such as node failures and data availability. The system changes replication parameters (number of copies, which nodes to replicate to) based on actual needs, rather than maintaining constant fixed storage allocation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7657543B1Method and system for creating and using shadow roots
Publication Date: 2010.02.02 ORACLE AMERICAN INC
  • US7657543B1 patent drawing
  • US7657543B1 patent drawing
  • US7657543B1 patent drawing

AI summary

A method for storing a first copy of an object, including obtaining the object including a globally unique identifier (GUID), generating a first derived GUID using the GUID of the object, storing the first copy of the object identified by the first derived GUID in a root node of the object, publishing possession of the first copy of the object identified by the first derived GUID by the root node of the object, associating a first shadow root with the first copy of the object, and storing the first copy of the object identified by the GUID in the first shadow root.