Hierarchical Consensus Scheme with Geo-Aware Leader Election
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing consensus algorithms in geographically distributed data centers face challenges in maintaining data consistency across multiple data centers, particularly due to the risk of replicated data inconsistency and inefficiencies in communication protocols like Paxos and Raft, which can lead to increased latency and network traffic.
Innovation Solution
A cross-data center hierarchical consensus scheme with geo-aware leader election, where data centers are grouped into clusters using a leader-based approach (Raft) for local consensus and peer-to-peer communication for inter-cluster consensus, with leaders selected based on usage frequency and geographic proximity, ensuring efficient data replication and reduced latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a leader-based approach (Raft) is used for consensus, then communication efficiency is improved (single round-trip), but system complexity increases due to leader election and geo-aware selection mechanisms
Solution Approach 1:
The system segments data centers into geographic clusters, with each cluster having its own leader. This segmentation allows the complex geo-aware leader election to be distributed across multiple independent clusters rather than requiring a single global leader, reducing overall system complexity while maintaining communication efficiency within each cluster.
Solution Approach 2:
The patent introduces a geographic dimension to leader selection, moving beyond simple random or round-robin approaches. By considering geographic proximity and usage frequency as additional dimensions, the system optimizes communication efficiency for geographically distributed data centers while managing complexity through structured selection criteria.
2Reliability
If geographically distributed data centers are used, then fault tolerance is improved, but data consistency becomes harder to maintain
Solution Approach 1:
The patent applies local quality by having different data centers in different geographic locations serve different regional clients. Each data center maintains local data consistency independently through its own leader-follower relationships, while geographic distribution provides fault tolerance. This allows the system to maintain data consistency locally while achieving fault tolerance globally.
Solution Approach 2:
The leader acts as an intermediary that coordinates write operations across follower data centers. When a write operation occurs, the leader ensures all necessary followers are updated before confirming the write, thus maintaining data consistency across geographically distributed data centers while preserving fault tolerance.
3Speed
If all client requests are directed to a single leader, then consensus speed is improved, but network traffic increases to the leader data center
Solution Approach 1:
The patent segments the system into multiple geographic clusters, each with its own leader. This segmentation distributes the request load across multiple leaders rather than concentrating all traffic on a single leader, reducing network traffic to any single data center while maintaining fast consensus within each cluster through the leader-based approach.
Solution Approach 2:
Clients are directed to leaders in their geographic region rather than a single centralized leader. This local quality approach reduces network traffic by routing requests to the nearest leader, minimizing transmission distance and energy consumption while maintaining consensus speed through the efficient leader-based protocol.
Data Source
AI summary
A device comprises a non-transitory memory storage comprising instructions, a network interface, and one or more processors in communication with the memory storage and the network interface. The one or more processors execute the instructions to receive, via the network interface, a write request from a client device; send, via the network interface, the received write request to a set of follower devices; receive, via the network interface, a first acknowledgment from a majority of the follower devices of the set of follower devices that the write request was processed; send, via the network interface, the received write request to a set of peer devices; receive, via the network interface, second acknowledgments from a majority of the set of peer devices that the write request was processed; and send an acknowledgment of the write request to the client device in response to the receipt of the first acknowledgments and the second acknowledgments.