Consensus-Based Authority Selection in Replicated Block Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, managing replica consistency and health in distributed block storage systems is challenging due to potential miscommunication among replicas, leading to inefficiencies and system instability, particularly in multi-attach configurations where network failures can cause incorrect health assessments and flip-flop scenarios between master and secondary replicas.

Innovation Solution

Implementing a consensus-based protocol among replicas to periodically communicate and verify each other's status, using a strongly consistent data store for authoritative replica configuration management, and incorporating a generation number mechanism to prevent simultaneous master status grants, thus allowing replicas to detect failures and update configurations autonomously without relying on external systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If replicas periodically communicate and verify each other's status using a consensus-based protocol, then replica consistency and system stability are improved, but communication overhead and system complexity increase

Engineering Contradiction:
Improvereplica consistencyVSAvoidcommunication protocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a consensus-based protocol where replicas periodically exchange heartbeat messages and verify each other's status. This feedback mechanism ensures that all replicas have a consistent view of the system state and can detect failures promptly, resolving the contradiction by making the complexity worthwhile for achieving reliability

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses a strongly consistent data store to pre-establish authoritative replica configuration before failures occur. This preliminary setup allows replicas to autonomously detect failures and update configurations without relying on external systems during critical moments, improving consistency while managing complexity through advance preparation

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If a strongly consistent data store is used for authoritative replica configuration management, then configuration accuracy is improved, but system performance and access speed decrease

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidsystem performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent pre-establishes authoritative replica configuration in a strongly consistent data store before failures occur. This preliminary action ensures that when failures happen, replicas can quickly autonomously detect and update configurations without real-time external system dependency, achieving both accuracy and performance

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables replicas to autonomously detect failures and update their configurations without relying on external systems during critical operations. This self-service capability reduces ongoing performance overhead while maintaining configuration accuracy through the pre-established authoritative data store

Inventive Principle:
Principle #25Self-service

3Reliability

If generation number mechanism is implemented to prevent simultaneous master status grants, then system stability is improved, but additional computational overhead is introduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements a generation number mechanism that prevents simultaneous master status grants by establishing a clear ordering and authority hierarchy before conflicts can occur. This preliminary anti-action approach blocks potential flip-flop scenarios and stability issues before they arise, with the low computational cost of comparing generation numbers making the overhead negligible

Inventive Principle:
Principle #9Preliminary anti-action

4Productivity

If replicas autonomously detect failures and update configurations without external systems, then system efficiency is improved, but risk of miscommunication and incorrect health assessments increases

Engineering Contradiction:
Improvesystem efficiencyVSAvoidhealth assessment accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a consensus-based protocol where replicas exchange heartbeat messages and verify each other's status through multiple communication rounds. This feedback mechanism allows autonomous failure detection while mitigating miscommunication risks through cross-validation among replicas

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent pre-establishes authoritative replica configuration in a strongly consistent data store before failures occur. This preliminary action provides a trusted reference that guides autonomous failure detection and configuration updates, reducing the risk of incorrect health assessments while maintaining system efficiency

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11288004B1Consensus-based authority selection in replicated network-accessible block storage devices
Publication Date: 2022.03.29 AMAZON TECH INC
  • US11288004B1 patent drawing
  • US11288004B1 patent drawing
  • US11288004B1 patent drawing

AI summary

Systems and methods are provided to manage replicas of a virtualized block storage volume. The master replica of the virtualized block storage volume can heartbeat with each secondary replica of the virtualized block storage volume to provide an indication of the status of the master replica. Each secondary replica can reply to the heartbeat of the master replica. Each replica can be configured to request an updated replica configuration based on not receiving a heartbeat from one of the replicas. The master replica can request an updated replica configuration after a first time period without receiving a reply from one of the secondary replicas and each secondary replica can request an updated replica configuration after a second time period without receiving a communication from the master replica. Use of the heartbeat process between the master replica and the secondary replicas can increase system speed or reduce power consumption.