Multi-server Blockchain Node Heartbeat Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain nodes experience poor stability and service processing efficiency due to reliance on single servers, leading to instability and inefficiency in service processing and consensus networks.
Innovation Solution
Implementing a blockchain node with multiple servers and a registration center to manage server addresses, ensuring that service requests are distributed across available servers, thereby enhancing stability and efficiency by allowing service requests to be processed even if one server is unavailable.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a blockchain node uses a single server for service processing, then the device complexity is reduced, but the stability and reliability of the node deteriorates
Solution Approach 1:
The blockchain node is segmented into multiple independent servers (first server, second server, third server) that can operate independently. Each server can process service requests and perform consensus operations separately, so that if one server fails, the others can continue to maintain node functionality and network consensus.
Solution Approach 2:
The patent implements beforehand cushioning by configuring multiple servers before any failure occurs. The system prepares redundant server instances that can immediately take over if a server fails, preventing stability deterioration before it happens. The registration center and heartbeat detection mechanisms are pre-configured to monitor and manage server availability proactively.
2Device complexity
If a blockchain node uses a single server, then the device complexity is low, but the service processing efficiency deteriorates due to limited software and hardware resources
Solution Approach 1:
The service processing function is segmented across multiple servers, allowing parallel processing of service requests. Different servers can handle different requests simultaneously, increasing the overall service processing capacity and efficiency of the blockchain node without requiring a single overly complex server.
Solution Approach 2:
Each server in the blockchain node is designed with universal functionality to perform both service processing and consensus operations. This multi-functionality allows any available server to handle any task, maximizing resource utilization and improving overall system efficiency through flexible workload distribution.
3Reliability
If a blockchain node uses multiple servers, then the stability and reliability improve, but the device complexity increases
Solution Approach 1:
The registration center acts as an intermediary that manages the complexity of multiple servers. It handles server address registration, updates, and coordination automatically, so that other components don't need to directly manage the complexity of multiple server instances. This intermediary abstracts the complexity away from individual nodes.
Solution Approach 2:
The system implements self-service mechanisms where servers automatically register their addresses with the registration center, and the registration center automatically notifies other nodes of server availability changes. The heartbeat detection mechanism automatically monitors server status without requiring manual intervention, allowing the system to self-manage the complexity of multiple servers.
4Reliability
If the system uses heartbeat detection messages to monitor servers, then the reliability improves through continuous availability checking, but the loss of time increases due to detection overhead
Solution Approach 1:
The system uses periodic heartbeat detection messages sent at regular intervals to monitor server availability. This periodic action balances reliability monitoring with time efficiency - frequent enough to detect failures promptly, but spaced sufficiently to minimize detection overhead. The registration center sends heartbeat messages at optimized intervals to maintain reliability without excessive time loss.
Data Source
AI summary
One example method performed by a registration center includes obtaining addresses of a first plurality of servers of a first blockchain node in a consensus network, where the consensus network further includes a plurality of additional blockchain nodes, where each blockchain node of the plurality of additional blockchain nodes includes a corresponding plurality of servers; sending the addresses of the first plurality of servers to each blockchain node of the plurality of additional blockchain nodes and a client for storage; sending a heartbeat detection message to a first server of the first plurality of servers; determining that a response message to the heartbeat detection message is not returned by the first server in a predetermined time period; determining that the first server is offline; and instructing each blockchain node of the plurality of additional blockchain nodes to delete an address of the first server.