Quorum-Based Replication for Distributed Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data record replication approaches face performance bottlenecks due to node slowness or failure, affecting consistency, fault tolerance, and scalability in distributed data storage systems.

Innovation Solution

A quorum-based replication system that allows write operations to commit as long as a majority of replica nodes acknowledge, reducing the need for waiting on all nodes and minimizing the impact of slow or failed nodes, with a message exchange scheme to update commitment status and facilitate durable record visibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all replica nodes must acknowledge before write operation commits, then data consistency is improved, but write performance deteriorates due to node slowness or failure

Engineering Contradiction:
Improvedata consistencyVSAvoidwrite performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by requiring only a quorum (majority) of replica nodes to acknowledge a write operation instead of all nodes. This allows the system to commit writes with sufficient redundancy for consistency while avoiding blocking on slow or failed nodes, thus resolving the contradiction between data consistency and write performance

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If write operations wait for all node acknowledgments, then fault tolerance is improved, but latency increases

Engineering Contradiction:
Improvefault toleranceVSAvoidwrite latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system requires only a quorum of acknowledgments rather than all nodes, providing sufficient fault tolerance to tolerate node failures while significantly reducing write latency by not waiting for slow or failed nodes

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the acknowledgment threshold parameter from requiring all nodes to requiring only a quorum (majority), which adjusts the system's fault tolerance level while dramatically improving latency characteristics

Inventive Principle:
Principle #35Parameter changes

3Reliability

If strict acknowledgment protocols are enforced, then data consistency is maintained, but system scalability deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

By requiring only a quorum of acknowledgments rather than all nodes, the system maintains data consistency through sufficient redundancy while improving scalability by reducing the coordination overhead and blocking behavior that limits system growth

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10366106B2Quorum-based replication of data records
Publication Date: 2019.07.30 SAP SE
  • US10366106B2 patent drawing
  • US10366106B2 patent drawing
  • US10366106B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for quorum-based replication of data records. In one embodiment, a read request for reading a record is received from a user node on a replica node of a cluster of replica nodes. The record is then determined not committed on the replica node. In response to the determination, an update message indicative of whether the number of replica nodes on which the record is durable exceeds a threshold is received on the replica node. In response to the number of replica nodes exceeds the threshold, a value of the record on the replica node is transmitted to the user node.