Container Migration Proxy Queuing Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing container migration techniques result in downtime, leading to data loss during the migration process, and do not allow for continuous processing of data within the container.
Innovation Solution
A container migration device that transitions the operation mode of the migration source proxy from a transfer mode to a queuing mode, allowing data to be saved instead of transferred, and then transitions to a queue sendout mode to send the saved data to the migration destination proxy, ensuring seamless data transmission and minimizing downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the container is stopped for migration, then the container can be moved to another device, but data is lost and processing continuity is interrupted
Solution Approach 1:
The patent applies preliminary action by having the migration source proxy save incoming requests and data to a queue before the container is stopped for migration. This ensures that no data is lost during the transition period, as all incoming data is pre-captured in the queue and will be forwarded to the migration destination proxy after the container resumes operation.
Solution Approach 2:
The patent uses the migration source proxy and migration destination proxy as intermediary components that mediate between the request source container and the migrating container. The proxy saves data in a queue during migration and forwards it afterward, acting as a buffer that maintains data continuity without requiring the container itself to remain operational.
2Ease of operation
If the container is stopped for migration, then the container can be moved, but requests and data cannot be transmitted to the stopped container
Solution Approach 1:
The migration source proxy serves as an intermediary that receives requests and data from the request source container even when the target container is stopped. It saves this data in a queue and forwards it to the migration destination proxy after the container resumes, ensuring seamless request handling without requiring direct container availability.
Solution Approach 2:
The system performs preliminary action by capturing and saving all incoming requests and data in the migration source proxy's queue before the container is stopped. This pre-capture mechanism ensures that no requests are lost during migration, and they are systematically processed after the container becomes operational again.
3Loss of time
If differential transfer of container image is used, then downtime is shortened, but downtime is not reduced to zero and data loss still occurs
Solution Approach 1:
The patent extends the preliminary action principle by not only saving data before container stop but also maintaining the queue operational during the entire migration process. The migration source proxy continuously saves incoming data to the queue even when the container is stopped, ensuring zero data loss while the container image is being transferred differentially.
Solution Approach 2:
The proxy acts as a persistent intermediary that decouples the data transmission path from the container operational state. It receives, saves, and forwards data independently of whether the container is running or being migrated, eliminating the data loss problem that persists even with differential transfer techniques.
Data Source
AI summary
A container migration device causes an operation mode of a migration source proxy (120) to transition from a transfer mode of: receiving data being transmitted from a request source container (110) that requests data processing; and transferring the received data to a migration source container (130) being a request destination container, to a queuing mode of saving the data instead of transferring. After the operation mode of the migration source proxy transitions to the queueing mode and the migration destination container (150) is activated, the container migration device causes the operation mode of the migration source proxy to transition to a queue sendout mode of sending out the saved data to a migration destination proxy. After sendout of the saved data is completed, the container migration device causes the request source container to change a data transmission destination from the migration source proxy to a migration destination proxy (140).


