Zero Downtime Topology Updates for Distributed Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed service provider systems face challenges in efficiently managing and updating the topology of distributed data storage, leading to potential downtime and data access issues.

Innovation Solution

The implementation of a zero-downtime topology update process for distributed data storage systems, which involves periodic health status queries of data nodes, updating the topology file accordingly, and pausing and resuming data access requests to ensure seamless updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If topology updates are performed in traditional distributed storage systems, then the storage structure can be updated to reflect current data locations, but the system experiences downtime during the update process

Engineering Contradiction:
Improvesystem availabilityVSAvoiddowntime during topology update
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically switches between old and new topology files during updates. The router service monitors the health status of the new topology file and can switch back to the old topology if the new one proves defective, enabling continuous operation without downtime while maintaining system reliability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary validation by writing the new topology file to disk and checking its health status before fully activating it. This preliminary action allows the system to detect potential issues before they affect service continuity, preventing downtime caused by defective topology updates

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the router service continuously monitors and validates topology files, then system reliability is improved, but the complexity of the update process increases

Engineering Contradiction:
Improvetopology file validityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The router service automatically monitors the health status of topology files and performs self-healing by switching back to the old topology file if the new one is defective. This self-service mechanism improves reliability without requiring complex manual intervention or additional external monitoring systems

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a feedback loop where the router service continuously checks the health status of the new topology file and automatically responds by switching topologies if issues are detected. This feedback mechanism ensures reliability while keeping the update process manageable through automated decision-making

Inventive Principle:
Principle #23Feedback

3Measurement precision

If health status checks are performed frequently, then the accuracy of topology information is improved, but the system consumes more resources

Engineering Contradiction:
Improvehealth status accuracyVSAvoidprocessing resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system performs continuous health status monitoring of topology files without interruption, ensuring always-current accuracy of topology information. The monitoring is integrated into the normal operation flow, allowing accurate measurements without requiring separate dedicated resource allocations

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS20250173327A1Systems and methods for zero downtime topology updates for distributed data storage
Publication Date: 2025.05.29 STRIPE LLC
  • US20250173327A1 patent drawing
  • US20250173327A1 patent drawing
  • US20250173327A1 patent drawing

AI summary

A method and apparatus for updating data router nodes in a distributed storage system are described. The method can include querying, by a first database agent of a database node, a cache data store for health status metrics of the cache data store. The method can also include storing, by the first database agent of the database node, the health status metrics in a data repository. Furthermore, the method can include obtaining, by a second database agent of a router node, the health status metrics from the data repository, and updating, by the second database agent of the router node, a database topology file based on the health status metrics.