Container Checkpoint Resource Limit Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing checkpoint/restart operations in Linux containers lose resource limits and result in an inconsistent execution environment for processes before and after the operation.
Innovation Solution
A method and apparatus that acquire and checkpoint configuration information, control group status parameters, and application program status parameters at the checkpoint stage, and read and configure these parameters to maintain consistency in the execution environment during the restart stage, ensuring resource limits are preserved.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a freezing subsystem is used to suspend execution during checkpoint/restart, then the container can be checkpointed and restarted, but resource limits are lost and execution environment becomes inconsistent
Solution Approach 1:
The patent applies preliminary action by capturing and storing control group status parameters (including resource limits) before the checkpoint operation is performed. This allows the execution environment configuration to be preserved and restored during restart, preventing the loss of resource limits that occurs in traditional checkpoint/restart implementations.
Solution Approach 2:
The patent uses copying by creating a snapshot of the control group status parameters and storing them in an image file. This copied information is then used to restore the execution environment after restart, ensuring consistency between the pre-checkpoint and post-restart states without requiring the original control group configuration to persist.
2Ease of manufacture
If control group parameters are not preserved during checkpoint, then the checkpoint operation is simpler, but resource limits are lost after restart
Solution Approach 1:
The patent extracts control group status parameters (such as CPU limits, memory limits, and other resource constraints) from the running container and stores them separately in an image file. This extraction allows the checkpoint operation to remain simple while preserving the resource limit information that would otherwise be lost during the checkpoint/restart cycle.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Embodiments of the present invention disclose a method and an apparatus for checkpointing and restarting a container status. The method for checkpointing and restarting a container status according to the embodiments of the present invention includes: at a checkpoint stage, acquiring and checkpointing configuration information of a first container, a control group status parameter of the first container, and an application program status parameter of the first container; and at a restart stage, reading the configuration information of the first container, the control group status parameter of the first container, and the application program status parameter of the first container, and configure a second container according to the read configuration information of the first container, the read control group status parameter of the first container, and the read application program status parameter of the first container. The embodiments of the present invention further disclose the apparatus for checkpointing and restarting a container status, so that an execution environment of a process in the container can be kept consistent before and after a checkpoint/restart operation.