Distributed Data Store Volume Recovery Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed data storage systems face challenges in maintaining data consistency and facilitating recovery operations due to the complexity and resource intensity of synchronization protocols, which can hinder maintenance and support tasks, leading to reduced performance and reliability.

Innovation Solution

Implementing a distributed data store that allows multiple recovery agents to access and recover data volumes, enabling independent recovery operations and transitioning the data volume state to a recovery state to allow write access, thereby reducing dependency on a single writer and expediting recovery processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronization protocols are used to ensure data consistency across storage nodes, then data consistency is maintained, but the time and resources required to perform changes consistently increase

Engineering Contradiction:
Improvedata consistencyVSAvoidtime required to perform changes
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the write operation into two independent parts: (1) accepting the write request and updating the data, and (2) sending notifications to other storage nodes. This segmentation allows the write operation to complete quickly without waiting for synchronization, while consistency is maintained through asynchronous notifications and version tracking.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-establishing version identifiers and tracking mechanisms before write operations occur. When a write request is received, the system can immediately process it with the pre-configured versioning infrastructure in place, avoiding the need for time-consuming synchronization protocols during the actual write operation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If synchronization protocols are used to ensure data consistency across storage nodes, then data consistency is maintained, but the resources required to perform changes consistently increase

Engineering Contradiction:
Improvedata consistencyVSAvoidresources required to perform changes
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of using complex synchronization protocols that require extensive communication and coordination between storage nodes, the patent uses simple version identifier copies. Each storage node maintains a copy of the version identifier, allowing independent verification of data consistency without resource-intensive synchronization operations.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Each storage node independently manages its own version tracking and consistency verification using the version identifiers provided by the system. This self-service approach eliminates the need for centralized coordination and reduces the overall resource requirements for maintaining consistency across the distributed system.

Inventive Principle:
Principle #25Self-service

3Reliability

If consistency schemes are implemented, then data consistency is ensured, but maintenance and support tasks such as recovery are delayed or inhibited

Engineering Contradiction:
Improvedata consistencyVSAvoidmaintenance and support task performance
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts the recovery capability from the single writer constraint by introducing a dedicated recovery agent that operates independently. This recovery agent can access and restore data from storage nodes without being blocked by the consistency schemes that protect normal write operations, as it uses alternative mechanisms such as version identifiers and backup data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces version identifiers as an intermediary mechanism that facilitates both consistency maintenance and recovery operations. These version identifiers serve as a common language between the consistency protocol and recovery processes, allowing recovery agents to verify and restore data consistency without being inhibited by the presence of active writers or complex synchronization protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If a single writer consistency scheme is used, then data consistency is maintained, but multiple recovery agents cannot access the data volume simultaneously

Engineering Contradiction:
Improvedata consistencyVSAvoidrecovery agent access
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adjusts access permissions based on the operational context. During normal write operations, a single writer consistency scheme is enforced. However, during recovery operations, the system dynamically allows multiple recovery agents to access the data volume simultaneously by using version identifiers and state tracking to maintain consistency without blocking recovery processes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the consistency parameter from a static single-writer model to a dynamic model that allows different access patterns based on operational state. By introducing version identifiers and tracking the operational state (write mode vs. recovery mode), the system can switch between consistency enforcement levels, allowing multiple recovery agents to access data simultaneously when in recovery mode while maintaining consistency guarantees.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9424140B1Providing data volume recovery access in a distributed data store to multiple recovery agents
Publication Date: 2016.08.23 AMAZON TECH INC
  • US9424140B1 patent drawing
  • US9424140B1 patent drawing
  • US9424140B1 patent drawing

AI summary

A distributed data store may provide volume recovery access to multiple recovery agents. A data volume may be maintained for a storage client at the distributed data store. Write access to the data volume may be granted according to a single writer consistency scheme. When a recovery event is detected for the data volume, the data volume may be made available to multiple recovery agents that may perform respective recovery operations. Upon first completion of a recovery operation for the data volume, granting access to the data volume according to the single writer consistency scheme may be resumed. In some embodiments, the distributed data store may be a log-structured data store.