Interval-Controlled Replication Coordinator Node

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern distributed storage environments face challenges in ensuring data integrity and availability, particularly during unplanned events or disasters, as existing replication methods may not adequately manage data consistency and latency across nodes, leading to potential data loss and operational disruptions.

Innovation Solution

Interval-controlled replication is implemented, where a coordinator node sends interval indications to nodes, ensuring that data writes are completed and acknowledged across primary and secondary storage systems within specific intervals, preventing dependent writes until all nodes have moved to the next interval, thereby maintaining data consistency and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional replication methods are used, then data availability is improved, but data consistency and integrity deteriorate due to lack of coordination between nodes

Engineering Contradiction:
Improvedata availabilityVSAvoiddata consistency
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

A coordinator node is introduced as an intermediary to manage replication intervals and coordinate write operations across all nodes. The coordinator sends interval indication messages to control when nodes can proceed with writes, ensuring that replication operations are synchronized and data consistency is maintained while preserving availability through the distributed architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If synchronous replication is implemented to ensure data consistency, then data integrity is improved, but application I/O latency increases

Engineering Contradiction:
Improvedata integrityVSAvoidapplication I/O latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements periodic replication intervals controlled by the coordinator node. Instead of synchronous confirmation for each write operation, nodes operate in periodic intervals where the coordinator manages the timing of replication operations. This allows applications to proceed with I/O operations without waiting for remote replication confirmation, reducing latency while maintaining data integrity through controlled interval-based synchronization

Inventive Principle:
Principle #19Periodic action

3Loss of time

If replication intervals are shortened to reduce latency, then application performance is improved, but data consistency risks increase due to network delays and node failures

Engineering Contradiction:
Improvereplication latencyVSAvoiddata consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The coordinator node implements feedback mechanisms by monitoring node status and interval completion. The coordinator sends interval indication messages that provide feedback to nodes about when it is safe to proceed with write operations. This feedback loop allows the system to dynamically manage replication intervals, ensuring that nodes only commit writes when the coordinator confirms it is safe to do so, thereby maintaining data consistency even with shorter intervals

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The coordinator node performs preliminary actions by sending interval indication messages before nodes execute write operations. This preliminary coordination ensures that all nodes are synchronized and ready to proceed with replication at the appropriate time, preventing data consistency issues that could arise from premature or uncoordinated writes

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2820531B1Interval-controlled replication
Publication Date: 2018.08.22 GEN DIGITAL INC
  • EP2820531B1 patent drawingFigure 1
  • EP2820531B1 patent drawingFigure 2A
  • EP2820531B1 patent drawingFigure 2B

AI summary

Various systems and methods for interval-controlled replication are described. For example, one method involves a node receiving a first interval indication indicating start of a first interval. After receiving the first interval indication, an application on the node initiates a first write, which includes the node initiating a first local write and a first remote write. The first local write accesses a local storage. The first remote write accesses a remote storage and replicates the first local write. The node waits for acknowledgements indicating that the local and remote writes have finished, as well as for a second interval indication, before the first write from the application is treated being complete.