Multi-zone Data Center Failover via Leader Node Replication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional methods for managing data center failures, such as those caused by disasters like fires or earthquakes, often result in interruptions to Internet-based services and irreparable data loss due to the lack of effective data replication across multiple zones.

Innovation Solution

A method and apparatus for managing multi-zone data center failures by allocating data nodes across different regions, with a leader management node and backup nodes using data replication modes that prioritize either data stability or latency reduction, enabling failover without access address changes and enhancing availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is replicated only within a single data center, then data access speed is improved, but system reliability deteriorates due to vulnerability to single-point failures from disasters

Engineering Contradiction:

Improvedata access speedVSAvoidsystem reliability

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The system segments data storage across multiple independent data centers (first data center and second data center) rather than concentrating all data in one location. This segmentation ensures that a disaster affecting one data center does not result in total data loss, thereby improving reliability while maintaining access speed through distributed architecture

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a geographical dimension to data replication by establishing data nodes in different physical locations (first data center and second data center). This spatial distribution across multiple zones provides redundancy against localized disasters while maintaining fast access through proximity-based node selection

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Reliability

If data is replicated across multiple data centers, then system reliability is improved, but data access speed deteriorates due to increased distance

Engineering Contradiction:

Improvesystem reliabilityVSAvoiddata access speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The system implements local quality by designating primary data nodes in each data center that serve their respective locations, ensuring fast local access. Simultaneously, backup data nodes are established in remote data centers for reliability. The system intelligently selects between local and remote nodes based on operational status, optimizing both speed and reliability

Inventive Principle:

Principle #3Local quality

3Stability of the object's composition

If synchronous replication is used between data centers, then data consistency is improved, but latency increases

Engineering Contradiction:

Improvedata consistencyVSAvoidreplication latency

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system dynamically adjusts replication behavior based on operational conditions. During normal operations, asynchronous replication is used to minimize latency. Upon detecting failures or requiring enhanced consistency, the system transitions to synchronous replication modes, providing flexible adaptation to different operational requirements

Inventive Principle:

Principle #15Dynamics

4Loss of time

If asynchronous replication is used between data centers, then latency is reduced, but data consistency deteriorates

Engineering Contradiction:

Improvereplication latencyVSAvoiddata consistency

Core Design Contradiction:

Loss of timeVSStability of the object's composition

Solution Approach 1:

The system dynamically switches between asynchronous and synchronous replication modes based on operational needs. Asynchronous replication provides low-latency operations during normal conditions, while the system can transition to synchronous modes when data consistency becomes critical or during failover scenarios

Inventive Principle:

Principle #15Dynamics

5Adaptability or versatility

If failover requires access address changes, then routing flexibility is improved, but service continuity deteriorates due to client reconfiguration needs

Engineering Contradiction:

Improverouting flexibilityVSAvoidservice continuity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements self-service failover where the distributed data node architecture automatically detects failures and redirects traffic to backup nodes without requiring client-side reconfiguration. The transparent failover mechanism maintains service continuity while the underlying system dynamically adapts routing, separating client experience from system flexibility

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS20240378123A1Methods and apparatuses for managing multi-zone data center failures

Publication Date: 2024.11.14 NAVER CORP

AI summary

A method for managing data center failures, executed by one or more processors of a leader management node, includes allocating a first data node among a first plurality of data nodes a master data node, the first plurality of data nodes being in a first data center, allocating a second data node among the first plurality of data nodes as a first backup data node, allocating one among a second plurality of data nodes as a second backup data node, the second plurality of data nodes being in a second data center, and the first data center and the second data center being located in different regions, and setting a data replication mode between the master data node, the first backup data node and the second backup data node, the data replication mode being selected from a set of modes including a first mode and a second mode.