DNS Alias Synchronization for Replicated Storage Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In replicated object storage systems, client applications face burdensome redirects when objects are unavailable on the primary system due to corruption, downtime, or node failure, requiring manual intervention for failover scenarios.
Innovation Solution
Implementing an 'eventually consistent' method for DNS alias synchronization across systems in a replicated environment, where each system maintains updated information on replication links and DNS aliases, allowing network requests to be processed on behalf of other systems without direct communication, thus eliminating the need for manual redirects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual redirecting is implemented for failover scenarios, then system reliability is improved, but operation complexity and time consumption increase
Solution Approach 1:
The system automatically manages failover by having the primary Storage Manager detect object unavailability and autonomously redirect client requests to replica Storage Managers. This self-service mechanism eliminates the need for manual customer intervention while maintaining system reliability.
Solution Approach 2:
The system pre-establishes replication links and DNS alias mappings before failover is needed. When the primary system fails, the redirect logic is already in place, enabling immediate automatic failover without requiring manual configuration or intervention.
2Loss of information
If direct communication between all systems is required, then information accuracy is improved, but device complexity increases
Solution Approach 1:
The patent introduces a DNS alias synchronization mechanism as an intermediary that indirectly shares system status information between all participants. Instead of requiring direct communication channels between every pair of systems, the DNS alias acts as a centralized information repository that all systems can query to learn about replication topology and failover status.
3Ease of operation
If automatic failover is implemented, then ease of operation is improved, but system complexity increases
Solution Approach 1:
The patent replaces manual mechanical intervention (customer redirecting requests) with an automated software-based DNS alias synchronization mechanism. The Storage Managers automatically update DNS aliases to reflect current system status, enabling seamless automatic failover without increasing operational complexity for users.
Data Source
AI summary
A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into a plurality of systems each having multiple nodes. The systems have one or more replication links each being formed to indicate replication of data from one system to another system in a replicated environment where each system is configured as a sub-domain in a Domain Name System (DNS) infrastructure. A DNS alias synchronization method comprises maintaining updated information, within each system, of all replication links involving that system and of DNS aliases of other systems associated with all replication links involving that system (S602-S607). This enables that system to process network-based requests, on behalf of the other systems, without redirecting the requests from the other systems to that system.