Stateful Session Failover Across Multi-Core Appliances
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to maintain seamless operation of stateful sessions across multi-core appliances during failover scenarios, leading to service disruptions when primary intermediaries become unavailable.
Innovation Solution
A Stateful Session Failover module dynamically synchronizes session information from a primary multi-core appliance to a secondary appliance, ensuring persistence by distributing sessions across multiple cores and establishing connections for failover, using a timer-based synchronization mechanism to ensure continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If session information is synchronized from primary appliance to secondary appliance during failover, then service continuity is maintained, but system complexity increases due to synchronization mechanisms
Solution Approach 1:
The system performs preliminary synchronization of session information from the primary appliance to the secondary appliance before failover occurs. The SSF module proactively pushes session states, configurations, and settings to the secondary appliance, ensuring that when failover is needed, the secondary appliance is already prepared with all necessary session data to maintain service continuity without interruption.
2Productivity
If session states are distributed across multiple cores in multi-core appliances, then processing capacity increases, but session consistency during failover becomes more difficult to maintain
Solution Approach 1:
The SSF module merges session information from multiple cores of the primary appliance into a unified session state representation. It aggregates session states, configurations, and settings from all cores and pushes this consolidated information to the secondary appliance, ensuring that the secondary appliance receives a complete and consistent view of all sessions regardless of which core they originated from.
Solution Approach 2:
The SSF module acts as an intermediary between the multi-core primary appliance and the secondary appliance. It receives session information from various cores, standardizes and consolidates the data, and then pushes it to the secondary appliance. This intermediary role ensures session consistency across the failover boundary while allowing each appliance to maintain its multi-core architecture for high processing capacity.
3Extent of automation
If timer-based synchronization is used to push session information, then synchronization is automated, but synchronization timing may cause service disruption during failover
Solution Approach 1:
The system implements a timer-based synchronization mechanism where the SSF module periodically pushes session information from the primary appliance to the secondary appliance. The timer provides automated feedback-driven synchronization, ensuring that session states are updated at regular intervals. This automated approach reduces manual intervention while maintaining up-to-date session information on the secondary appliance, minimizing service disruption during failover.
Data Source
AI summary
The present disclosure presents systems and methods for maintaining operation of stateful sessions by a secondary multi-core appliance upon failover of a first multi-core appliance. A stateful session failover module of primary appliance may receive session states from each of the cores of the primary appliance. The stateful session failover module may communicate the session states of the cores of the primary appliance to a stateful session failover module of the secondary appliance. The stateful session failover module of the secondary appliance may update each of the cores of the secondary appliance with the session states. Upon failover, cores of the secondary appliance may maintain operation and features of the sessions handled by the primary appliance prior to failover using the received state sessions for each session maintained.