Switching Device Migrated Connection Table DIP Change Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing load balancing methods in cloud solutions fail to address client connectivity disruptions and connection retries due to changes in Direct IP (DIP) address assignments, leading to performance degradation in virtual address environments.
Innovation Solution
A method and apparatus that maintain per-connection consistency by using a connection tracking table in management logic and a migrated connection table in a switching device, which includes hardware and software components, to manage virtual-to-direct address mappings and handle changes in DIP assignments, ensuring seamless communication even after DIP updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Direct IP (DIP) address pools are updated to improve load balancing adaptability, then the load balancer can better distribute traffic to available servers, but client connectivity disruptions occur and connections break due to changes in DIP assignment
Solution Approach 1:
The system performs preliminary actions by detecting DIP changes before they affect client connections. The management logic monitors DIP pool updates and proactively updates the connection tracking table and main mapping unit before connectivity disruptions occur, preventing broken connections rather than reacting after they happen.
Solution Approach 2:
The system implements feedback mechanisms where the management logic continuously monitors DIP address pool status and connection states. When DIP changes are detected, the system feedbacks this information to update the connection tracking table and main mapping unit, ensuring the load balancing configuration reflects current server availability and maintains connection reliability.
2Reliability
If connection tracking table is maintained in management logic to track per-connection state, then connection consistency can be maintained across DIP updates, but system complexity increases due to additional tracking requirements
Solution Approach 1:
The connection tracking table acts as an intermediary data structure between the main mapping unit and the DIP address pool. It stores per-connection state information and mapping relationships, mediating the interaction between DIP changes and active connections. This intermediary layer simplifies the complexity by providing a centralized location to track and update connection states without modifying the core switching fabric.
3Adaptability or versatility
If main mapping unit is updated with new DIP assignments to reflect current server availability, then load balancing can adapt to server changes, but existing client connections may be disrupted due to mapping changes
Solution Approach 1:
The system performs preliminary updates to the connection tracking table before modifying the main mapping unit. By detecting DIP changes first and updating connection state information in advance, the system prepares the mapping relationships so that when the main mapping unit is updated, existing connections can be seamlessly redirected without disruption, maintaining throughput while adapting to server changes.
Data Source
AI summary
A method including providing: a switching device including a main mapping unit configured to provide a main mapping which maps virtual addresses to direct addresses; management logic configured to store a connection tracking table stored in memory and configured for storing a plurality of connection mappings each including a virtual-to-direct mapping from a virtual address to a direct address; and a migrated connection table stored in memory and configured for storing a plurality of migrated connection mappings each including a virtual-to-migrated-direct mapping from a virtual address to a migrated direct address. Upon receiving an indication that a direct address has changed: when the indication that a direct address has changed includes an indication that a direct address stored in one or more connection mappings in the connection tracking table is not active, copying the one or more connection mappings from the connection tracking table to the migrated connection table, when the indication that a direct address has changed includes an indication that a new direct address has become active, creating one or more connection mappings in the migrated connection table, and altering the main mapping in accordance with the direct address change.