Data Replication via State Marker and Channel Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing systems, the replication of data can result in 'in-flight' changes being missed, leading to potential inconsistencies, as changes made by processes before the intention to create a new replica are not always captured, jeopardizing data consistency.

Innovation Solution

A method is introduced where a state marker message is used to announce the intention to replicate data, and communication channels are monitored to ensure all changes are transmitted and received before replicating, stabilizing the data to prevent newer data from being overwritten by older data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data replication is performed by copying existing replicas, then replication speed is improved, but data consistency deteriorates due to missed in-flight changes

Engineering Contradiction:
Improvereplication speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary actions by announcing the replication intention in advance and establishing a new communication channel before the actual data copy occurs. This allows in-flight changes to be redirected to the new channel, ensuring they are not lost during replication. The state marker message is sent beforehand to prepare the system for the upcoming replication event.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A new communication channel acts as an intermediary between the data region and processes during the replication transition. This intermediary channel captures all changes made during the replication window, including in-flight changes, and ensures they are properly transferred to the new replica. The intermediary prevents direct conflicts between old and new replica updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If changes are transmitted to all existing replicas, then data redundancy is improved, but the risk of overwriting newer data with older replicated data increases

Engineering Contradiction:
Improvedata redundancyVSAvoiddata freshness
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system announces the replication intention in advance before copying data, allowing all processes to be notified and prepare for the replication event. This preliminary notification ensures that subsequent changes are directed through the new communication channel, preventing older data from overwriting newer changes after replication occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The communication channel is made dynamic by creating a new channel during replication and transitioning processes from the old channel to the new one. This dynamic channel transition ensures that data flow is continuously updated to reflect the current replica state, preventing stale data from being applied after newer changes have been made.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8180729B2Data replication method
Publication Date: 2012.05.15 VMWARE INC
  • US8180729B2 patent drawing
  • US8180729B2 patent drawing
  • US8180729B2 patent drawing

AI summary

To ensure data consistency for a new data replica created for a computing system, the transmission and receipt of messages altering the data are monitored and replication of the data is permitted when all changes to the data that have been transmitted to the data have been received.