Distributed MMDB Token Controller Automatic Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing distributed Main Memory Database (MMDB) systems face reliability and stability issues due to complex deployment methods, manual switch delays, and poor automatic detection mechanisms, leading to potential failures and increased costs.
Innovation Solution
A method and system for implementing a distributed MMDB that periodically transmits and receives node information between token controllers, processes transactions based on priority, and automatically selects a new master token controller upon breakdown, eliminating the need for dual machine control software and Active-Standby dual machine solutions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Active-Standby dual machine solution is used with manual switch, then system reliability is improved through redundancy, but switch delay increases and automation is reduced
Solution Approach 1:
The system implements automatic failover detection and execution through the third node monitoring the heartbeat between primary and standby nodes. When the primary node fails, the standby node automatically takes over without manual intervention, making the system self-healing and eliminating switch delay caused by manual operations.
Solution Approach 2:
The third node continuously monitors the heartbeat signals between primary and standby nodes, providing real-time feedback on system health. This feedback mechanism enables automatic detection of failures and triggers the failover process, reducing switch delay and improving response time.
2Loss of time
If Active-Standby dual machine solution with automatic detection is used, then switch delay is reduced, but system complexity increases due to heartbeat monitoring infrastructure
Solution Approach 1:
The third node serves multiple functions simultaneously: it acts as a backup node for failover purposes and as a monitoring node for heartbeat detection. This merging of roles reduces the need for separate monitoring infrastructure, simplifying deployment while maintaining automatic failover capability.
Solution Approach 2:
The third node is designed with multi-functionality, serving both as a standby database node and as a monitoring node that detects failures between primary and standby nodes. This universal design reduces system complexity by eliminating dedicated monitoring hardware or software.
3Reliability
If dual machine control software is deployed, then failover capability is improved, but deployment complexity and cost increase
Solution Approach 1:
The patent extracts the monitoring function from complex dual-machine control software and implements it through a simple third node that monitors heartbeat signals. This extraction simplifies the system by removing the need for sophisticated control software while maintaining failover capability.
Solution Approach 2:
Instead of using complex control software to manage failover, the system uses a simplified approach where the third node copies the heartbeat monitoring function from traditional active-standby systems. This copying of essential functionality with simplified implementation reduces deployment complexity and cost.
4Extent of automation
If heartbeat monitoring at third point is implemented, then automatic detection is improved, but failure risk increases due to single point of failure
Solution Approach 1:
The third node is designed as a cushioning element that protects against failures in the primary-standby communication channel. By monitoring heartbeat signals from an independent position, it provides a backup detection mechanism that prevents single points of failure from causing system-wide failures.
Solution Approach 2:
The third node acts as an intermediary that mediates the monitoring function between primary and standby nodes. Rather than having nodes directly monitor each other (creating potential failure points), the third node intermediates the detection process, reducing failure risk while maintaining automatic detection capability.
Data Source
Figure 1~2
Figure 3~5
Figure 6
AI summary
Method, equipment and main memory data cluster, for implementing distribute-type memory database system are provided, which relates to the field of communication technology and resolve the technical problem of poor reliability of distribute-type memory database in prior art. The method of the embodiment main comprising: transmitting messages comprising node memory database information to at least two token controller; respectively receiving messages comprising memory database list from the at least two token controllers, wherein the memory database list comprises information within a cluster arranged according to at least one of the node memory database information; and processing transactions within the cluster according to the information within the cluster in the memory database list. The solution applies to memory database.