Session Synchronization via Cold UDP Channel for Load Balancer Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing session synchronization mechanism based on hot synchronization in four-layer load balancer clusters fails to ensure complete restoration of sessions on a failed node, leading to service damage due to the lack of continuous service traffic.
Innovation Solution
A session synchronization method that employs a cold synchronization mechanism, where negotiation messages are sent between nodes to establish a UDP message channel for synchronizing sessions, ensuring complete restoration of sessions even without continuous service traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If hot synchronization mechanism is used to synchronize sessions in real-time, then synchronization speed is improved, but session integrity cannot be ensured when service traffic is not continuous
Solution Approach 1:
The patent implements cold synchronization that activates when a failed node comes online, performing preliminary session restoration before normal service resumption. This preliminary action ensures session integrity is established in advance, preventing the loss that occurs with hot synchronization when traffic is intermittent.
Solution Approach 2:
The patent introduces a dual synchronization mechanism where cold synchronization acts as an intermediary backup when hot synchronization fails to maintain session integrity. The system switches between hot and cold synchronization modes based on node status, ensuring session integrity is maintained through the intermediary cold synchronization process.
2Use of energy by moving object
If hot synchronization is performed only when service traffic is present, then resource consumption is reduced, but session restoration completeness deteriorates
Solution Approach 1:
The patent implements periodic cold synchronization checks when nodes come online after failure, regardless of whether service traffic is present. This periodic action ensures session information is restored completely at regular intervals (when nodes fail and recover), preventing information loss while consuming resources only periodically rather than continuously.
Solution Approach 2:
The system performs self-service by automatically detecting node failures and initiating cold synchronization when nodes come online, without requiring continuous external intervention or monitoring. This self-service mechanism ensures session restoration completeness while minimizing resource consumption by activating only when necessary.
3Reliability
If cold synchronization is implemented to ensure complete session restoration, then session integrity is improved, but synchronization complexity increases
Solution Approach 1:
The patent implements a dynamic synchronization system that automatically switches between hot synchronization (for normal operation) and cold synchronization (for failure recovery). This dynamic approach maintains session integrity through cold synchronization when needed while keeping the system simple during normal operation, avoiding permanent complexity increases.
Solution Approach 2:
The system changes synchronization parameters based on node status - using hot synchronization during normal operation and switching to cold synchronization when nodes fail and recover. This parameter change approach ensures session integrity is maintained through parameter adjustment rather than through permanently complex synchronization mechanisms.
Data Source
AI summary
Provide are a session synchronization method, a session synchronization apparatus, a session synchronization system, a first node, a second node, and a medium. The session synchronization method includes sending a first negotiation message to at least one node in a cluster through a first central processing unit (CPU) core and determining a second node according to at least one received second negotiation message; sending a third negotiation message to the second node through the first CPU core; in the case where a fourth negotiation message sent from the second node is received through the first CPU core, receiving the user datagram protocol (UDP) message sent from the second node through a second CPU core; and synchronizing the session of the second node according to the UDP message through the second CPU core.