Distributed Database Failover via Centralized Health-State Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional distributed database frameworks struggle to resume operation following a primary node failure when nodes are unable to communicate directly with each other, leading to potential data loss or downtime.
Innovation Solution
A centralized management module within a customer's private cloud manages health state information of distributed database nodes using heartbeat signals and remote procedure calls, designating a secondary node as primary in case of failure without direct node communication, and establishing secure connections with public cloud resources for health state sharing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If nodes are configured to communicate health state information directly with each other, then the distributed database framework can automatically determine primary and secondary node designations, but the system becomes vulnerable when nodes are isolated or unable to communicate directly
Solution Approach 1:
The patent introduces a centralized management module as an intermediary that collects health state information from all database nodes and distributes it among them. This mediator enables nodes to determine primary/secondary designations even when they cannot communicate directly, resolving the contradiction between reliability during isolation and communication complexity by centralizing the communication function.
2Reliability
If a centralized management module is introduced to manage health state information, then node failure recovery is enabled even with communication isolation, but the system complexity increases
Solution Approach 1:
The patent merges the health state management function into the existing centralized management module (such as vCenter), combining multiple functions (resource management, health monitoring, node designation control) into a single integrated component. This reduces overall system complexity despite adding centralized management capabilities by leveraging existing infrastructure rather than adding separate dedicated systems.
Solution Approach 2:
The centralized management module is designed to perform multiple functions: managing overall cloud resources, monitoring health state of database nodes, distributing health information, and controlling node designations. This multi-functionality justifies the added complexity by providing comprehensive management capabilities that benefit the entire system rather than just the distributed database framework.
3Ease of operation
If health state information is shared through public cloud resources, then remote access and monitoring are enabled, but security risks and credential exposure increase
Solution Approach 1:
The patent extracts the health state information from the sensitive authentication context and transmits it separately through secure channels. The management module shares only the health state data with public cloud resources without exposing credentials or authentication mechanisms, thereby enabling remote monitoring while eliminating credential exposure risks.
Solution Approach 2:
The patent implements different communication modes for different purposes: secure direct communication for credential exchange between nodes and the management module, and controlled information sharing for health state data with public cloud resources. This localized approach to security ensures that sensitive authentication information remains protected while still enabling remote monitoring capabilities where needed.
Data Source
AI summary
A distributed database management system includes a centralized management module for managing resources within a customer network. The management module software, e.g., vCenter, or a health state plugin of the management module, accesses health state information from distributed database nodes within the customer network. The health state information may be or may include a simple signal, analogous to a heartbeat signal, that each functional node generates periodically and sends to the management module. The nodes may include a primary node to maintain a database and one or more secondary nodes to replicate the database. The primary and secondary nodes may be nodes within an edge node cluster of the customer network. The edge node cluster may be implemented within an infrastructure appliance, e.g., VxRail. The management module shares the health state information with the nodes and controls, based on the health state information, the designation of a primary node and secondary nodes.