CN112817692A

CN112817692A - Resource recovery method, device, apparatus, medium, and program product

Info

Publication number: CN112817692A
Application number: CN202110133174.5A
Authority: CN
Inventors: 钱建辉
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2021-05-18
Anticipated expiration: 2041-01-29
Also published as: CN112817692B

Abstract

The present disclosure provides a resource recycling method for a container, comprising: acquiring performance index data of a target container, wherein the performance index data is used for representing the resource use condition of the target container, and the target container provides computing resources for an application program running in the target container; acquiring running environment data of a target container, wherein the running scene is used for representing a hardware running environment and a software running environment of the target container; determining whether the target container meets the resource recovery condition based on the statistical result of the performance index data and/or the operation scene data; and if the resource recovery condition is satisfied, recovering the resource of the target container. The present disclosure also provides a resource recovery apparatus for a container, an electronic device, a computer-readable storage medium, and a program product. The resource recovery method and device for the container provided by the disclosure can be applied to the financial field or other fields.

Description

Resource recovery method, device, apparatus, medium, and program product

Technical Field

The present disclosure relates to the field of container technology, and in particular, to a method, apparatus, device, medium, and program product for resource recovery.

Background

With the rapid development of cloud platforms, a Container (Container) technology capable of simplifying the construction, deployment and operation processes of application programs is developed, so that more and more application programs are subjected to containerization, a resource applicant is required to apply for computing resources, the Container is started and deployed, and the application programs are integrated into the Container and run. In a research and development environment, the application amount of computing resources increases at a geometric speed, and the contradiction between the originally relatively limited resource supply amount and the continuously increasing resource demand amount is aggravated.

Solutions are also provided in the related art for alleviating the resource supply-demand contradiction by recycling resources so as to facilitate the application of resources by other resource applicants, such as active return or due return by the resource applicants. However, in the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the prior art: these "passive" resource recycling methods still have the problem of unreasonable resource occupation or waste of idle resources.

Disclosure of Invention

In view of the above, in order to at least partially overcome the above technical problems of the related art using a "passive" resource recycling manner, the present disclosure provides an "active" resource recycling manner, which can improve the resource recycling efficiency of a container, avoid unreasonable occupation of resources, and accelerate the rolling of idle resources. The present disclosure provides a resource recovery method, apparatus, device, medium, and program product for a container.

To achieve the above object, one aspect of the present disclosure provides a resource reclamation method for a container, which may include: acquiring performance index data of a target container, wherein the performance index data is used for representing resource use conditions of the target container, the target container provides computing resources for running an application program in the target container, and acquiring running environment data of the target container, wherein the running scene is used for representing a hardware running environment and a software running environment of the target container, determining whether the target container meets a resource recovery condition based on a statistical result of the performance index data and/or the running scene data, and recovering the resources of the target container if the resource recovery condition is met.

According to an embodiment of the present disclosure, the collecting performance index data of the target container may include: the method comprises the steps of collecting first performance index data corresponding to a target container and a processor resource, collecting second performance index data corresponding to a target container and a memory resource, collecting third performance index data corresponding to a target container and a file system resource, and collecting fourth performance index data corresponding to a target container and a network resource.

According to an embodiment of the present disclosure, the determining whether the target container satisfies a resource recycling condition based on the statistical result of the performance index data may include: determining a first fluctuation value corresponding to the processor resource based on a statistical result of the first performance indicator data in a first statistical period, determining a second fluctuation value corresponding to the memory resource based on a statistical result of the second performance indicator data in a second statistical period, determining a third fluctuation value corresponding to the file system resource based on a statistical result of the third performance indicator data in a third statistical period, determining a fourth fluctuation value corresponding to the network resource based on a statistical result of the fourth performance indicator data in a fourth statistical period, and determining whether the target container satisfies a resource recovery condition based on the first fluctuation value, the second fluctuation value, the third fluctuation value, and the fourth fluctuation value, wherein the first statistical period, the second statistical period, the third fluctuation value, and the fourth fluctuation value, The third statistical period and the fourth statistical period may be the same or different.

According to an embodiment of the present disclosure, the determining whether the target container satisfies a resource recycling condition based on the first fluctuation value, the second fluctuation value, the third fluctuation value, and the fourth fluctuation value may include: determining that the processor resource satisfies a resource reclamation condition if the first fluctuation value is less than a first threshold value, determining that the memory resource satisfies a resource recycling condition when the second fluctuation value is smaller than a second threshold value, determining that the file system resource satisfies a resource recycling condition when the third threshold value is smaller than a third threshold value, determining that the network resource satisfies a resource recovery condition in a case where the fourth fluctuation value is smaller than a fourth threshold value, and determining whether the target container satisfies a resource reclamation condition in case that at least two of the processor resource, the memory resource, the file system resource, and the network resource satisfy the resource reclamation condition, the first threshold, the second threshold, the third threshold, and the fourth threshold may be the same or different.

According to an embodiment of the present disclosure, the collecting the operating environment data of the target container may include: and collecting log data of the target container corresponding to the log indexes and collecting version data of the target container, wherein the version data is used for representing version information of the application program.

According to an embodiment of the present disclosure, the determining whether the target container satisfies a resource recycling condition based on the statistical result of the operation scenario data may include: determining a fifth fluctuation value corresponding to the log index based on a statistical result of the log data in a fifth statistical period, and determining whether the target container meets a resource recovery condition based on the fifth fluctuation value and the version data, wherein the fifth statistical period may be the same as or different from the first statistical period, the second statistical period, the third statistical period, and the fourth statistical period.

According to an embodiment of the present disclosure, the determining whether the target container satisfies a resource recycling condition based on the fifth fluctuation value and the version data may include: and determining that the target container meets a resource recycling condition when the fifth fluctuation value is smaller than a fifth threshold, and determining that the target container meets the resource recycling condition when the version data representation is inconsistent with the version information of the application program, wherein the fifth threshold may be the same as or different from the first threshold, the second threshold, the third threshold, and the fourth threshold.

According to an embodiment of the present disclosure, the recovering the resource of the target container may include: and releasing the processor resources and the memory resources occupied by the target container according to the recycling priority, and releasing the occupation of the target container on the file system resources under the condition that the occupation of the file system resources exceeds a preset time length.

To achieve the above object, another aspect of the present disclosure provides a resource recycling apparatus for a container, which may include: the system comprises a first acquisition module, a second acquisition module, a determination module and a recovery module, wherein the first acquisition module is used for acquiring performance index data of a target container, the performance index data is used for representing the resource use condition of the target container, the target container provides computing resources for running an application program in the target container, the second acquisition module is used for acquiring running environment data of the target container, the running scene is used for representing the hardware running environment and the software running environment of the target container, the determination module is used for determining whether the target container meets a resource recovery condition or not based on the statistical result of the performance index data and/or the running scene data, and the recovery module is used for recovering the resource of the target container if the resource recovery condition is met.

According to an embodiment of the present disclosure, the first collecting module may include: the system comprises a first acquisition submodule used for acquiring first performance index data corresponding to a target container and a processor resource, a second acquisition submodule used for acquiring second performance index data corresponding to the target container and a memory resource, a third acquisition submodule used for acquiring third performance index data corresponding to the target container and a file system resource, and a fourth acquisition submodule used for acquiring fourth performance index data corresponding to the target container and a network resource.

According to an embodiment of the present disclosure, the determining module may include: a first fluctuation value determination sub-module for determining a first fluctuation value corresponding to the processor resource based on a statistical result of the first performance index data in a first statistical period, a second fluctuation value determination sub-module for determining a second fluctuation value corresponding to the memory resource based on a statistical result of the second performance index data in a second statistical period, a third fluctuation value determination sub-module for determining a third fluctuation value corresponding to the file system resource based on a statistical result of the third performance index data in a third statistical period, a fourth fluctuation value determination sub-module for determining a fourth fluctuation value corresponding to the network resource based on a statistical result of the fourth performance index data in a fourth statistical period, and a first recovery condition determination sub-module for determining a first fluctuation value corresponding to the network resource based on the first fluctuation value, And determining whether the target container meets a resource recovery condition according to the second fluctuation value, the third fluctuation value and the fourth fluctuation value, wherein the first statistical period, the second statistical period, the third statistical period and the fourth statistical period may be the same or different.

According to an embodiment of the present disclosure, the first recovery condition determining sub-module may include: a first reclamation condition determining unit configured to determine that the processor resource satisfies a resource reclamation condition if the first fluctuation value is smaller than a first threshold value, a second reclamation condition determining unit configured to determine that the memory resource satisfies a resource reclamation condition if the second fluctuation value is smaller than a second threshold value, a third reclamation condition determining unit configured to determine that the file system resource satisfies a resource reclamation condition if the third fluctuation value is smaller than a third threshold value, a fourth reclamation condition determining unit configured to determine that the network resource satisfies a resource reclamation condition if the fourth fluctuation value is smaller than a fourth threshold value, and a fifth reclamation condition determining unit configured to determine that the processor resource, the memory resource, the file system resource, and the network resource satisfy a resource reclamation condition if at least two of the processor resource, the memory resource, the file system resource, and the network resource satisfy a resource reclamation condition, and determining whether the target container meets a resource recovery condition, wherein the first threshold, the second threshold, the third threshold and the fourth threshold may be the same or different.

According to an embodiment of the present disclosure, the second collecting module may include: the device comprises a first acquisition submodule and a second acquisition submodule, wherein the first acquisition submodule is used for acquiring log data of the target container, the log data correspond to log indexes, the second acquisition submodule is used for acquiring version data of the target container, and the version data are used for representing version information of the application program.

According to an embodiment of the present disclosure, the determining module may include: a fifth fluctuation value determining submodule, configured to determine a fifth fluctuation value corresponding to the log index based on a statistical result of the log data in a fifth statistical period, and a second recovery condition determining submodule, configured to determine whether the target container satisfies a resource recovery condition based on the fifth fluctuation value and the version data, where the fifth statistical period may be the same as or different from the first statistical period, the second statistical period, the third statistical period, and the fourth statistical period.

According to an embodiment of the present disclosure, the second recovery condition determining sub-module may include: a sixth recovery condition determining unit, configured to determine that the target container satisfies a resource recovery condition if the fifth fluctuation value is smaller than a fifth threshold, and a seventh recovery condition determining unit, configured to determine that the target container satisfies the resource recovery condition if the version data representation does not match the version information of the application program, where the fifth threshold may be the same as or different from the first threshold, the second threshold, the third threshold, and the fourth threshold.

According to an embodiment of the present disclosure, the recycling module may include: a first releasing submodule for firstly releasing the processor resource and the memory resource occupied by the target container according to the recycling priority, and a second releasing submodule for releasing the occupation of the target container to the file system resource when the occupation of the file system resource exceeds a preset time length.

In order to achieve the above object, another aspect of the present disclosure provides an electronic device including: one or more processors, a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method for resource reclamation for containers as described above.

To achieve the above object, another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the resource reclamation method for a container as described above when the instructions are executed.

To achieve the above object, another aspect of the present disclosure provides a computer program comprising computer executable instructions for implementing the method for resource reclamation for containers as described above when executed.

According to the active resource recovery mode provided by the disclosure, not only can the performance data of the container be monitored in real time, but also whether the container meets the resource recovery condition can be determined according to the analysis result of the performance data, if yes, the container resource can be timely recovered, the technical problems that resources are unreasonably occupied or idle resources are wasted due to the fact that resources are initiatively returned by resource applicants or the passive resource recovery mode of returning the resources due to maturity in the related technology can be at least partially overcome, and therefore the timely recovery of the container resource can be realized, not only can the resource waste caused by unreasonable occupation of the idle resources be avoided, but also the dependence of resource returning on manpower can be relieved, the automation of resource release is realized, and the technical effect of the recovery efficiency of the container resource is improved.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario of a resource reclamation method and apparatus applicable to a container in accordance with an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a resource reclamation method that may be applied to a container in accordance with an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow diagram of a resource reclamation method that may be applied to a container in accordance with another embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow diagram of a resource reclamation method that may be applied to a container, in accordance with another embodiment of the present disclosure;

FIG. 5 schematically illustrates a block diagram of a resource recovery device that may be applied to a container in accordance with an embodiment of the present disclosure;

FIG. 6 schematically illustrates a schematic diagram of a computer-readable storage medium product suitable for implementing the above-described resource reclamation method that may be applied to a container, in accordance with an embodiment of the present disclosure; and

fig. 7 schematically shows a block diagram of an electronic device adapted to implement the above described resource reclamation method applicable to containers according to an embodiment of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

It should be noted that the figures are not drawn to scale and that elements of similar structure or function are generally represented by like reference numerals throughout the figures for illustrative purposes.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components. All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable container resource recycling apparatus such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). The techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

The container cloud is an emerging product form in cloud computing in recent two years, the container is a lightweight virtualization technology in computing form, the container service is process-level virtualization form packaging, the container is started and deployed rapidly, the container can be deployed and scheduled rapidly according to resource requirements in an application layer, and the life cycle change speed is high. The process of integrating and running applications into containers that are generic to the applications is referred to as "containerization," which in particular simplifies the application building, deployment, and running process. The resource recovery method provided by the related art needs manual intervention for processing or recovery after the resources are expired, so that the resources which are idle but not expired cannot be timely recovered and reused, the idle resources are unreasonably occupied and cannot roll in time, and meanwhile, other resource applicant containers cannot apply for the originally utilizable waste, and the utilization rate of the resources is seriously influenced.

Accordingly, the present disclosure provides a resource reclamation method that may be applied to a container, which may include a data acquisition phase and a resource reclamation phase. In the data acquisition stage, on one hand, performance index data of the target container needs to be acquired, the performance index data is used for representing the resource use condition of the target container, the target container provides computing resources for running an application program therein, on the other hand, running environment data of the target container needs to be acquired, and the running scene is used for representing the hardware running environment and the software running environment of the target container. In the resource recovery stage, whether the target container meets the resource recovery condition is determined based on the statistical result of the performance index data and/or the operation scene data, and then the resources of the target container are recovered under the condition that the resource recovery condition is met, so that the resources are recovered in time.

Because the active resource recovery mode is provided by the disclosure, not only the performance data of each container can be monitored and obtained in real time, but also the container meeting the resource recovery condition can be determined according to the analysis result of the performance data, and the container resource can be recovered in time, not only can the proactive resource return by the resource applicant in the related art be overcome at least in part by the present disclosure, or those "passive" resource reclamation approaches that expire returning resources, result in resources that are unreasonably occupied, or the technical problem that idle resources are wasted, can at least partially realize the timely recovery of container resources, the technical effects of avoiding resource waste caused by unreasonable occupation of idle resources, relieving the dependence of resource return on manpower, automatically releasing resources and improving the recovery efficiency of container resources are achieved.

It should be noted that the resource recycling method and apparatus for containers provided by the present disclosure may be used in the financial field, and may also be used in any field other than the financial field. Therefore, the application field of the resource recycling method and device for containers provided by the present disclosure is not limited.

Fig. 1 schematically illustrates an application scenario 100 of a resource reclamation method and apparatus applicable to a container in accordance with an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of an application scenario to which the embodiment of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiment of the present disclosure may not be applied to other application scenarios.

As shown in fig. 1, an application scenario 100 of the resource reclamation method and apparatus that may be applied to a container may include a container centralized monitoring management platform 110, a container 120, and an application 130.

The container centralized monitoring management platform 110 shown in fig. 1 may be integrated with a container monitoring platform 111, a log platform 112, an application version management system 113, and a monitoring recycle function module 114. The container monitoring platform 111 may be a monitoring platform 1111 for container virtualization, or a self-developed container performance monitoring platform 1112. The container monitoring platform 111 is configured to provide index data corresponding to container dynamic indexes, which may include but are not limited to CPU, memory, file system, and network traffic, through the monitoring platform 1111 of container virtualization or the self-developed container performance monitoring platform 1112. The log platform 112 is used to provide container logs including, but not limited to, operation logs, system logs, and application logs. The application version management system 113 is used to provide version information where the container is located. The monitoring and recovering function module 114 is used for providing a collecting function of container-related data and a resource recovering decision and executing function, so as to implement decision of whether resources are recovered or not and automatic recovery, and improve the resource utilization rate.

The container 120 shown in fig. 1 may be a plurality of containers deployed on a cloud platform, and may include, but is not limited to, a container 121, a container 122, a container 123, a container 124, a container 125, and a container 126. The container can be a Linux container, which is based on kernel lightweight operating system layer virtualization technology, is another leap of developing, deploying and managing application modes, and is mainly realized by two major mechanisms, namely a Namespace (Namespace) with an isolation effect and a Cgram (control groups) with a resource management control effect. The Linux container mirror provides portability and version control to ensure applications that can run on developers' laptops and also run normally in a production environment. Compared with a virtual machine, the Linux container occupies less resources during operation, uses standard interfaces (starting, stopping, environment variables and the like) and can be isolated from the application; furthermore, it is easier to manage as part of a large application (containing multiple containers), and these multi-container applications can be orchestrated across multiple cloud environments. The container can also be a Docker container, and the Docker controls resource quotas used by the container through Cgroup, including three major aspects of a CPU, a Memory (Memory) and a disk, and basically covers common resource quotas and usage control. The Cgroup is a physical resource provided by the Linux kernel and capable of limiting, recording and isolating the use of a process group, and may include but is not limited to a CPU, a Memory, and a disk Input/Output (I/O), and is used by many items such as LXC and Docker to implement process resource control. The container may also be another container. The plurality of containers may be the same type of container or different types of containers.

Application 130 shown in FIG. 1 may be an application integrated in a container and may include, but is not limited to, application 131, application 132, application 133, application 134, application 135, and application 136. Where application 131 may be integrated in container 121, application 132 may be integrated in container 122, application 133 may be integrated in container 123, application 134 may be integrated in container 124, application 135 may be integrated in container 125, and application 136 may be integrated in container 126.

It should be noted that, depending on the actual situation of the application, one application may be integrated in one container, or may be integrated in multiple containers, and fig. 1 only shows the case where one application is integrated in one container, but should not be construed as a limitation on the number of integration relations between the application and the container. The number of containers and applications shown in fig. 1 is merely illustrative. There may be any number of containers and applications as desired for implementation, and the disclosure is not limited thereto.

FIG. 2 schematically shows a flow diagram of a resource reclamation method that may be applied to a container in accordance with an embodiment of the present disclosure. As shown in fig. 2, the method 200 may include operations S210 to S240.

In operation S210, performance index data of a target container is collected.

According to embodiments of the present disclosure, a container is a series of processes isolated from the rest of the system, and may share the same operating system kernel, isolating application processes from the rest of the system. The target container may be any one of a plurality of containers deployed on the cloud platform. For example, the container may be an LXC container or a Docker container.

According to an embodiment of the present disclosure, performance index data is used to characterize resource usage of a target container that provides computing resources for an application running therein.

It should be noted that, by default, the CPU share of each Docker container is 1024kb, and the share of a single container is meaningless, so that the CPU weighting effect of the containers is only shown when multiple containers are running simultaneously. For example, the CPU shares of the two containers A, B are 1000kb and 500kb, respectively, and when the CPU allocates time slices, the container a has twice more chance to acquire the CPU time slices than the container B, but the allocation result depends on the running states of the host and other containers at that time, and there is no guarantee that the container a can acquire the CPU time slices. For example, container A's process is always idle, then container B is available to fetch more CPU slots than container A. In the extreme case, say, only one container is run on the host, even if its CPU share is only 50kb, it can monopolize the CPU resources of the entire host. The Cgroup will only take effect if the container is allocated resources are scarce, that is to say if there is a need to restrict the resources used by the container. Therefore, it cannot be determined that a plurality of CPU resources are allocated to a certain container solely according to the CPU share of the container, and the resource allocation result depends on the CPU allocation of other containers running simultaneously and the running condition of the processes in the container.

According to the embodiment of the present disclosure, the performance index data of the target container may be collected through the monitoring platform 1111 of the container virtualization in the container monitoring platform 111 shown in fig. 1 according to a certain collection frequency, and may also be collected through the self-developed container performance monitoring platform 1112 in the container monitoring platform 111 shown in fig. 1. For example, performance indicator data may be collected every second. For example, the number of CPU indices, memory index data, and file system index data for a container may be collected from a monitoring platform for container virtualization or a self-developed container performance monitoring platform every second. The acquisition frequency in the present disclosure can be set manually as the case may be.

In operation S220, operating environment data of the target container is collected.

According to an embodiment of the present disclosure, the runtime scenario is used to characterize the hardware runtime environment and the software runtime environment of the target container. The hardware operating environment may be whether the container is executed with a start operation, a destroy operation, and other operating conditions, and the software operating environment may be software information, including but not limited to version information, of an application program running in the container. The runtime environment data may be log data and version data for the container, where the log data may include, but is not limited to, application logs, system logs, and user logs.

According to the embodiment of the disclosure, the operating environment data of the target container can be collected according to a certain collection frequency. For example, an application log, a system log, and a user log of a container may be collected from a logging platform every minute, and a version of the container may be collected from a version information management system every hour. It should be noted that the collection frequency of the version where the application log and the container are located may be the same or different, and the collection frequency may be determined according to the life cycle data of the container or may be determined according to human experience, which is not limited in this disclosure.

In operation S230, it is determined whether the target container satisfies a resource reclamation condition based on the statistical result of the performance index data and/or the operation scenario data.

According to an embodiment of the present disclosure, whether the target container satisfies the resource recycling condition may be determined based on the statistical result of the performance index data. In specific implementation, when the statistical result of the performance index data indicates that the computing resource usage rate of the target container is low and the usage rate changes little, indicating that the computing resource has been used completely or is in an unused state within a certain statistical period, it may be determined that the target container satisfies the resource recovery condition, and when the statistical result indicates that the computing resource usage rate of the target container is high and the usage rate changes little, indicating that the computing resource has not been used completely or is in an in-use state within a certain statistical period, it may be determined that the target container does not satisfy the resource recovery condition.

According to the embodiment of the disclosure, whether the target container meets the resource recycling condition may be determined based on the statistical result of the operation scene data. In specific implementation, when the statistical result of the operation scene data represents that the hardware or software resource usage rate of the target container is low and the usage rate changes little, it indicates that the hardware or software resource has been used completely or is in an unused state within a certain statistical period, at this time, it may be determined that the target container satisfies the resource recovery condition, and when the statistical result represents that the hardware or software resource usage rate of the target container is high and the usage rate changes little, it indicates that the hardware or software resource has not been used completely or is in an in-use state within a certain statistical period, at this time, it may be determined that the target container does not satisfy the resource recovery condition.

According to the embodiment of the disclosure, whether the target container meets the resource recovery condition may also be determined based on the statistical results of the performance index data and the operation scene data. In specific implementation, when the statistical result of the performance index data represents that the utilization rate of the computing resources of the target container is low, the fluctuation of the utilization rate is small, the statistical result of the data of the running scene represents that the hardware or software resource utilization rate of the target container is low, and the change of the utilization rate fluctuates little, which indicates that the computing resources, hardware or software resources are used completely, or in an unused state within a certain statistical period, at this time, it can be determined that the target container satisfies the resource recovery condition, and when the statistical result represents that the utilization rate of the computing resources of the target container is high and the fluctuation of the utilization rate is small, when the statistical result represents that the utilization rate of the hardware or software resources of the target container is high and the change of the utilization rate fluctuates, the fact that the computing resources, the hardware or the software resources are not used completely is shown, or in an in-use state within a certain statistical period, it may be determined that the target container does not satisfy the resource recycling condition.

It should be noted that, although the high and low of the resource usage are relative, for the sake of implementation, a threshold may be set for the resource usage to determine the high and low of the resource usage, so as to quantify the high and low of the resource usage. For example, for the memory index as an example, a first threshold 50% and a second threshold 10% of the memory resource usage rate may be set, if the memory usage rate is higher than the first threshold 50%, the memory resource usage rate may be determined to be high, and if the memory usage rate is lower than the second threshold 10%, the memory resource usage rate may be determined to be low. It is understood that, according to different resource indexes, the corresponding threshold values of the resource usage rate may be the same or different, and this disclosure does not limit this.

In operation S240, if the resource recovery condition is satisfied, the resource of the target container is recovered.

According to the embodiment of the present disclosure, since the resources applied by the target container to the platform are mainly computing resources provided by the application running therein, the resource recovery of the target container is naturally also for those computing resources that have been applied for before, and may include but is not limited to a CPU, a Memory (Memory), a disk resource, and a network resource. The recovery flow in the specific implementation of the container resource recovery may be to take the container offline, delete the container to release the resource of the host where the container is located, and finally delete the ledger information of the system related to the container, so that the resource can be timely recovered, and the recovered resource can be provided for other containers to apply for trial.

Through the embodiment of the disclosure, an active resource recovery mode is provided, which not only can monitor and obtain the performance data of the container in real time, but also can determine whether the container meets the resource recovery condition according to the analysis result of the performance data, if so, the resource of the container is recovered in time, thereby at least partially overcoming the problem that the resource is actively returned by a resource applicant in the related art, or those "passive" resource reclamation approaches that expire returning resources, result in resources that are unreasonably occupied, or the idle resources are wasted, so that the container resources can be timely recovered, the resource waste caused by unreasonable occupation of the idle resources can be avoided, the dependence of resource return on manpower can be eliminated, the automation of resource release is realized, and the technical effect of improving the recovery efficiency of the container resources is achieved.

As an alternative embodiment, the operation S210 (collecting the performance index data of the target container) may include: first performance index data corresponding to the target container and the processor resource is collected. And collecting second performance index data corresponding to the target container and the memory resource. And collecting third performance index data corresponding to the target container and the file system resource. And collecting fourth performance index data corresponding to the target container and the network resource.

According to an embodiment of the disclosure, the performance index may be a dynamic index of the container, and dynamic index data corresponding to the dynamic index may be used to characterize resource usage of the target container. Alternatively, the dynamic metrics may include, but are not limited to, a container CPU metric, a container memory metric, a container file system metric, and a container network metric.

Alternatively, the container CPU metrics may include, but are not limited to, system CPU cumulative elapsed time (container _ CPU _ system _ seconds _ total, unit: seconds), user CPU cumulative elapsed time (container _ CPU _ user _ seconds _ total, unit: seconds), container cumulative elapsed time on each CPU core (container _ CPU _ usage _ seconds _ total, unit: seconds). Optionally, the container memory metrics may include, but are not limited to, the maximum memory usage (container _ memory _ max _ usage _ bytes, unit: bytes) of the container, the current memory usage (container _ memory _ usage _ bytes, unit: bytes) of the container, the memory usage limit (container _ spec _ memory _ limit _ bytes) of the container, and the total memory amount (machine _ memory _ bytes) of the current host. Alternatively, the container file system indicators may include, but are not limited to, the amount of file system usage (container _ fs _ usage _ bytes, in bytes) in the container, the total amount of file system that the container can use (container _ fs _ limit _ bytes, in bytes), the total amount of container accumulated read data (container _ fs _ reads _ bytes _ total, in bytes), and the total amount of container accumulated write data (container _ fs _ writes _ bytes _ total, in bytes). Alternatively, the container network metrics may include, but are not limited to, the container network accumulating the total amount of received data (in bytes), and the container network accumulating the total amount of transmitted data (in bytes).

According to the embodiment of the disclosure, the breadth and the depth of data acquisition are considered from the aspect of representing the resource use condition of the target container, the first performance index data corresponding to the processor resource, the second performance index data corresponding to the memory resource, the third performance index data corresponding to the file system resource and the fourth performance index data corresponding to the network resource are respectively acquired, and based on the multi-dimensional index data of the processor resource, the memory resource, the file system resource and the network resource, multi-dimensional data support is provided for the resource use condition, so that the accuracy of a recovery decision is improved.

As an alternative embodiment, the aforementioned operation S230 (determining whether the target container satisfies the resource recycling condition based on the statistical result of the performance index data) may include: a first fluctuation value corresponding to the processor resource is determined based on statistics of the first performance indicator data over a first statistical period. And determining a second fluctuation value corresponding to the memory resource based on the statistical result of the second performance index data in the second statistical period. And determining a third fluctuation value corresponding to the file system resource based on the statistical result of the third performance index data in the third statistical period. And determining a fourth fluctuation value corresponding to the network resource based on the statistical result of the fourth performance index data in the fourth statistical period. And determining whether the target container meets the resource recovery condition based on the first fluctuation value, the second fluctuation value, the third fluctuation value and the fourth fluctuation value, wherein the first statistical period, the second statistical period, the third statistical period and the fourth statistical period may be the same or different.

According to the embodiment of the present disclosure, before performing operation S230, statistics on the performance index data is further required to obtain a statistical result, where the obtaining process of the statistical result is described as: for a plurality of performance indexes, the statistics and analysis of the index data are performed by using a plurality of time periods as time statistics dimensions, and the statistics of the performance index data corresponding to each performance index in a plurality of time periods, that is, the statistics of the performance index data, can be obtained. The plurality of time periods may be 1 day, 2 days, and 3 days, or 1 day, 2 days, 3 days, 4 days, and 5 days, and the number of time periods may be selected according to different performance indexes, which is not limited in this disclosure. Generally, the greater the number of time periods, the greater the number of samples of the statistical data, the greater the confidence in the statistical result, but in view of computational efficiency and ensuring the validity and validity of the statistical result, the time period will not exceed 30 days. Taking 1 day, 2 days, 3 days, 4 days and 5 days as time periods, calculating the utilization rate of the CPU, the usage amount of the memory, the read-write amount of the file system, and the network data receiving and transmitting amount as examples, and briefly explaining how to obtain the statistical result of the performance index data.

In specific implementation, the cumulative occupation time of the CPU in the container CPU index is counted, and the cumulative occupation time of the system CPU in 1 day, 2 days, 3 days, 4 days, and 5 days, the cumulative occupation time of the user CPU in 1 day, 2 days, 3 days, 4 days, and 5 days, and the cumulative occupation time of the container CPU in 1 day, 2 days, 3 days, 4 days, and 5 days can be obtained. The current memory usage of the container in the container memory index is counted, and the current memory usage of the container in 1 day, 2 days, 3 days, 4 days and 5 days can be obtained. Data statistics is carried out on the use amount of the file system in the container, the total amount of the accumulated read data of the container and the total amount of the accumulated write data of the container in the index of the file system of the container, so that the use amount of the file system, the total amount of the accumulated read data of the container and the total amount of the accumulated write data of the container in 1 day, 2 days, 3 days, 4 days and 5 days can be obtained. And performing data statistics on the total amount of the container network accumulated received data and the total amount of the container network accumulated transmitted data in the container network index to obtain the total amount of the container network accumulated received data and the total amount of the container network accumulated transmitted data within 1 day, 2 days, 3 days, 4 days and 5 days.

After obtaining the statistical result, optionally selecting two or more consecutive time periods of the plurality of time periods, determining a fluctuation value of the statistical value of the performance index data in the two or more consecutive time periods, and determining whether the target container satisfies the resource recovery condition based on the fluctuation value corresponding to each performance index. The multiple time periods may be 1 day, 2 days, 3 days, 4 days, and 5 days as a period, and optionally, more than two consecutive time periods may be two consecutive time periods, three consecutive time periods, or four consecutive time periods, which may be selected according to different performance indexes, which is not limited in this disclosure.

In specific implementation, based on the statistical result of the accumulated occupied time of the system CPU, the user CPU and the container CPU, the first fluctuation value of the system CPU, the user CPU and the container CPU in three consecutive periods (1 day, 2 days and 3 days) of 1 day, 2 days and 3 days can be determined. The second fluctuation value of the container over four consecutive cycles (1 day, 2 days, 3 days, 4 days or 2 days, 3 days, 4 days, 5 days) can be determined based on the statistics of the current memory usage of the container. Based on the statistics of the container file system usage and the cumulative total amount of read and write data, a third fluctuation value in two consecutive periods (1 day, 2 days or 2 days, 3 days) can be determined. Based on the statistics of the total amount of data received and transmitted accumulated by the container network, the fourth fluctuation value of the container network in two consecutive periods (1 day, 2 days or 2 days, 3 days) can be determined.

It should be noted that, because the CPU and the memory are often the most scarce resources, when determining whether the target container satisfies the resource recycling condition, the target container occupies a higher weight value than the file system and the network resource index, that is, the CPU sets the highest weight, the memory sets the next time, the file system sets the lowest weight, and the network resource sets the lowest weight.

Through the embodiment of the disclosure, the fluctuation value corresponding to each performance index can be determined based on the statistical result of each performance index data in the corresponding statistical period, whether the target container meets the resource recovery condition or not is determined based on the fluctuation values corresponding to a plurality of performance indexes, whether the container is recovered or not can be determined by using the fluctuation data of the container resource within a certain time range, the manual confirmation process can be decoupled, and the resource use efficiency is improved.

As an alternative embodiment, determining whether the target container satisfies the resource recovery condition based on the first fluctuation value, the second fluctuation value, the third fluctuation value, and the fourth fluctuation value may include: in the event that the first fluctuation value is less than a first threshold, it is determined that the processor resource satisfies a resource reclamation condition. And under the condition that the second fluctuation value is smaller than a second threshold value, determining that the memory resource meets the resource recovery condition. And under the condition that the third fluctuation value is smaller than a third threshold value, determining that the file system resource meets the resource recovery condition. And under the condition that the fourth fluctuation value is smaller than a fourth threshold value, determining that the network resource meets the resource recovery condition. And determining whether the target container meets the resource recycling condition under the condition that at least two of the processor resource, the memory resource, the file system resource and the network resource meet the resource recycling condition, wherein the first threshold, the second threshold, the third threshold and the fourth threshold may be the same or different.

According to the embodiment of the disclosure, after the fluctuation value corresponding to each performance index data is determined, a corresponding index threshold value can be set for each performance index, the threshold value is used for representing a lower limit value of resource recovery, under the condition that the fluctuation value is lower than the index threshold value, it is determined that the corresponding resource is not used, and whether the resource recovery condition is met is further determined by combining other performance indexes.

In a specific implementation, the first threshold may be 1%, and if the fluctuation value of the cumulative occupation time of the system, the user and the container CPU in three consecutive cycles is within 1%, the CPU resource of the container is considered to be unused. The second threshold may be 1%, and if the current memory usage amount of the container memory fluctuates within 1% in four consecutive cycles, the memory resource of the container is considered to be unused. The third threshold may be 10%, and if the container file system usage and the cumulative total amount of read and write data fluctuate by a value within 10% in two consecutive cycles, the disk resources of the container are considered unused. The fourth threshold may be 5%, and if the total amount of data cumulatively received and transmitted by the container network fluctuates within 5% in two consecutive periods, the network resource of the container is considered to be unused. The threshold corresponding to the performance index may be set empirically, and the disclosure is not limited thereto.

Through the embodiment of the disclosure, by judging the fluctuation value and the preset threshold value corresponding to each performance index data, whether the target container meets the resource recovery condition can be determined according to the fluctuation condition of the resource utilization rate, the applicant does not need to return actively or recover due, the recoverable resource in an idle state can be found in time, the resource utilization efficiency can be improved, and the resource rolling is accelerated.

As an alternative embodiment, the collecting the operating environment data of the target container may include: and collecting log data corresponding to the target container and the log indexes. And collecting version data of the target container, wherein the version data is used for representing version information of the application program.

According to an embodiment of the present disclosure, a container log may be obtained from the log platform 112 as shown in fig. 1, and the container log may include an operation log, a system log, and an application log.

According to the embodiment of the disclosure, besides the performance index of the container, the container log information and the version information are also acquired, whether the target container meets the resource recovery condition or not is determined from the multi-angle and multi-dimensional data, the accuracy of resource recovery decision can be improved, misjudgment and missed judgment are avoided, and the success rate of resource recovery is improved.

As an alternative embodiment, determining whether the target container satisfies the resource recycling condition based on the statistical result of the operation scenario data may include: and determining a fifth fluctuation value corresponding to the log index based on the statistical result of the log data in a fifth statistical period. And determining whether the target container meets the resource recovery condition or not based on a fifth fluctuation value and the version data, wherein the fifth statistical period may be the same as or different from the first statistical period, the second statistical period, the third statistical period and the fourth statistical period.

According to the embodiment of the present disclosure, in order to achieve consistency of data statistics periods, the present disclosure continues to use multiple time periods adopted in the foregoing performance index data statistics, and performs statistics on the operation scene data to obtain a statistical result.

In specific implementation, for the container log, the file sizes of the application log, the system log and the user log in 1 day, 2 days, 3 days, 4 days and 5 days can be obtained respectively.

After obtaining the statistics of the file sizes, the fluctuation value of the statistics of the file sizes of the logs, i.e. the statistics of the log data, in the two or more consecutive time periods may be determined for the plurality of time periods, optionally the two or more consecutive time periods. In specific implementation, the fifth fluctuation value of the application log, the system log and the user log in three consecutive periods (1 day, 2 days and 3 days) can be determined based on the statistical result of the file sizes of the application log, the system log and the user log. In addition, the embodiment of the present disclosure may also obtain container version information from the application version management system 113 as shown in fig. 1.

Through the embodiment of the disclosure, the fluctuation value of the file size can be determined based on the version information and the log information, whether the target container meets the resource recovery condition or not is determined, various recovery decision modes are provided, flexibility and diversity are achieved, and different recovery scenes are met.

As an alternative embodiment, the determining whether the target container satisfies the resource reclamation condition based on the fifth fluctuation value and the version data may include: and determining that the target container meets the resource recovery condition in the case that the fifth fluctuation value is smaller than a fifth threshold value. And under the condition that the representation of the version data is inconsistent with the version information of the application program, determining that the target container meets the resource recovery condition, wherein the fifth threshold value may be the same as or different from the first threshold value, the second threshold value, the third threshold value and the fourth threshold value.

According to the embodiment of the disclosure, after the fluctuation value corresponding to the container log is determined, a corresponding index threshold value can be set for the log file index, the threshold value is used for representing the lower limit value of resource recovery, under the condition that the fluctuation value is lower than the index threshold value, it is determined that no business transaction exists in the container, that is, the corresponding resource is not used, and whether the resource recovery condition is met is further determined by combining the container version information.

In a specific implementation, the fifth threshold may be 1%, and if the log sizes of the application log, the system log and the user log fluctuate within 1% in three consecutive periods, the container is considered to have no service transaction.

According to the embodiment of the disclosure, whether the recovery condition is met is determined by combining the log information and the version information of the container, a multi-dimensional judgment criterion is provided for judgment of a recovery decision, the accuracy of the resource recovery decision is improved, misjudgment and missed judgment are avoided, and the success rate of resource recovery is improved.

As an alternative embodiment, reclaiming resources of the target container may include: and releasing the processor resources and the memory resources occupied by the target container according to the recycling priority. And releasing the occupation of the file system resources by the target container under the condition that the occupation of the file system resources exceeds the preset time length.

According to an embodiment of the present disclosure, in a case that it is determined that the container resource needs to be recovered, a specific recovery flow may be: and calling a cloud platform interface to offline the container, and immediately deleting the container to release the CPU and the memory resource of the host. And the disk file can be deleted three days later for the container so as to facilitate the false deletion recovery. And finally, deleting the offline container disk files on the host machine after three days, and also deleting the ledger information of the container-related system.

Through the embodiment of the disclosure, the resources are released step by step in batches according to the importance of the resources, so that the stable release of the container resources can be realized, and the survival rate of resource recovery is improved.

FIG. 3 schematically illustrates a flow diagram of a resource reclamation method for a container according to another embodiment of the present disclosure. As shown in FIG. 3, the resource reclamation method 300 may include an old reclamation flow 310 and a new reclamation flow 320. The old recycling process 310 includes operations S311, and S330. The new recycling flow 320 includes operation S321, operation S322, operation S323, and operation S330. In operation S311, the expiration is returned. In operation S312, active return. In operation S330, reclamation is performed. In operation S321, data is collected. In operation S322, the decision is reclaimed. In operation S323, it is determined whether the recycling condition is satisfied, and if so, operation S330 is performed. Otherwise, operation S321 is performed.

Through the embodiment of the disclosure, when the container resource recovery process is initiated, manual confirmation is not needed, the purpose of releasing manpower is achieved, the container resource condition can be automatically monitored in real time in a multi-dimensional mode, the recovery process is insensitive to users, and efficient utilization of resources can be achieved.

FIG. 4 schematically illustrates a flow diagram of a resource reclamation method for a container according to another embodiment of the present disclosure. As shown in fig. 4, the method 400 may include operations S410 to S490.

In operation S410, the container recycle flow is culled from the old flow. In operation S420, the container recycle flow is changed to a new recycle path. In operation S430, a container monitoring module is designed and deployed, which includes a collection function (performance capacity data, log data, version data, and container life cycle data of a container) and a recovery decision function (determining whether a resource recovery condition is satisfied). In operation S440, the container monitoring module collects data (performance capacity data, log data, version data, container life cycle data of the container). Passed to the container reclamation decision function. In operation S450, the decision recovery function of the container monitoring module receives the data and performs a recovery decision. In operation S460, the container recycling decision function determines whether the container recycling meets a condition, and if so, transmits the container recycling information to a recycling process to initiate a recycling application. If the recovery condition is not satisfied, step S440 is executed to continue executing the round-robin collection job. If the recycle condition is satisfied, step S470 is performed. In operation S470, the container monitoring module transmits information of the recycling container to the execution recycling module. In operation S480, a recovery application is initiated, and the container is shut down, backed up, and the like to release the resource. In operation S490, the container monitoring module rejects the recycled container information from the container list.

Through the embodiment of the disclosure, the dependence on manpower and the waste of idle resources in the container resource recovery process can be avoided, the related resource recovery does not need to be processed manually or recovered due, the resource utilization rate can be improved, and the resource rollback is accelerated to recycle the resources again.

FIG. 5 schematically illustrates a block diagram of a resource reclamation apparatus for a container, in accordance with an embodiment of the present disclosure. As shown in fig. 5, the resource recovery apparatus 500 may include a first acquisition module 510, a second acquisition module 520, a determination module 530, and a recovery module 540.

The first collecting module 510 is configured to collect performance index data of a target container, where the performance index data is used to characterize resource usage of the target container, and the target container provides computing resources for an application running therein. Optionally, the first acquiring module 510 may be configured to perform operation S210 described in fig. 2, for example, and is not described herein again.

And a second collecting module 520, configured to collect operation environment data of the target container, where the operation scenario is used to represent a hardware operation environment and a software operation environment of the target container. Optionally, the second acquiring module 520 may be configured to perform operation S220 described in fig. 2, for example, and is not described herein again.

A determining module 530, configured to determine whether the target container satisfies the resource recycling condition based on the statistical result of the performance index data and/or the operation scenario data. Optionally, the determining module 530 may be configured to perform operation S230 described in fig. 2, for example, and is not described herein again.

And a recycling module 540, configured to recycle the resource of the target container if the resource recycling condition is satisfied. Optionally, the recycling module 540 may be configured to perform operation S240 described in fig. 2, for example, and is not described herein again.

As an alternative embodiment, the aforementioned first collecting module 510 may include: and the first acquisition submodule is used for acquiring first performance index data corresponding to the target container and the processor resource. And the second acquisition submodule is used for acquiring second performance index data corresponding to the target container and the memory resource. And the third acquisition submodule is used for acquiring third performance index data corresponding to the target container and the file system resource. And the fourth acquisition submodule is used for acquiring fourth performance index data corresponding to the target container and the network resource.

As an alternative embodiment, the aforementioned determining module 530 may include: and the first fluctuation value determination submodule is used for determining a first fluctuation value corresponding to the processor resource based on the statistical result of the first performance index data in the first statistical period. And the second fluctuation value determining submodule is used for determining a second fluctuation value corresponding to the memory resource based on the statistical result of the second performance index data in a second statistical period. And the third fluctuation value determining sub-module is used for determining a third fluctuation value corresponding to the file system resource based on a statistical result of the third performance index data in a third statistical period. And the fourth fluctuation value determining submodule is used for determining a fourth fluctuation value corresponding to the network resource based on the statistical result of the fourth performance index data in a fourth statistical period. And the first recovery condition determining submodule is used for determining whether the target container meets the resource recovery condition or not based on the first fluctuation value, the second fluctuation value, the third fluctuation value and the fourth fluctuation value, wherein the first statistical period, the second statistical period, the third statistical period and the fourth statistical period may be the same or different.

As an alternative embodiment, the first recycling condition determining sub-module may include: a first reclamation condition determining unit, configured to determine that the processor resource satisfies a resource reclamation condition if the first fluctuation value is smaller than a first threshold value. And the second recovery condition determining unit is used for determining that the memory resource meets the resource recovery condition under the condition that the second fluctuation value is smaller than the second threshold value. And the third recovery condition determining unit is used for determining that the file system resource meets the resource recovery condition under the condition that the third fluctuation value is smaller than the third threshold value. And a fourth recovery condition determining unit configured to determine that the network resource satisfies the resource recovery condition, in a case where the fourth fluctuation value is smaller than a fourth threshold value. A fifth recycling condition determining unit, configured to determine whether the target container satisfies a resource recycling condition when at least two of the processor resource, the memory resource, the file system resource, and the network resource satisfy the resource recycling condition, where the first threshold, the second threshold, the third threshold, and the fourth threshold may be the same or different.

As an alternative embodiment, the second collecting module 520 may include: and the fifth acquisition submodule is used for acquiring the log data of the target container corresponding to the log indexes. And a sixth acquisition submodule, configured to acquire version data of the target container, where the version data is used to represent version information of the application program.

As an alternative embodiment, the aforementioned determining module 530 may include: and the fifth fluctuation value determining submodule is used for determining a fifth fluctuation value corresponding to the log index based on the statistical result of the log data in a fifth statistical period. And a second recovery condition determining submodule, configured to determine whether the target container meets the resource recovery condition based on a fifth fluctuation value and the version data, where a fifth statistical period may be the same as or different from the first statistical period, the second statistical period, the third statistical period, and the fourth statistical period.

As an alternative embodiment, the second recovery condition determining submodule may include: a sixth recovery condition determining unit configured to determine that the target container satisfies the resource recovery condition, in a case where the fifth fluctuation value is smaller than a fifth threshold value. And a seventh recycling condition determining unit, configured to determine that the target container meets the resource recycling condition when the representation of the version data is inconsistent with the version information of the application program, where the fifth threshold may be the same as or different from the first threshold, the second threshold, the third threshold, and the fourth threshold.

As an alternative embodiment, the aforementioned recycling module 540 may include: and the first releasing submodule is used for firstly releasing the processor resources and the memory resources occupied by the target container according to the recycling priority. And the second release submodule is used for releasing the occupation of the target container on the file system resources under the condition that the occupation of the file system resources exceeds the preset time length.

It should be noted that, the implementation, solved technical problems, implemented functions, and achieved technical effects of each module in some embodiments of the resource recycling apparatus for a container are respectively the same as or similar to the implementation, solved technical problems, implemented functions, and achieved technical effects of each corresponding step in some embodiments of the resource recycling method for a container, and are not described herein again.

Any number of modules, sub-modules, units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units according to the embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of three implementations of software, hardware, and firmware, or in any suitable combination of any of them. Alternatively, one or more of the modules, sub-modules, units according to embodiments of the disclosure may be implemented at least partly as computer program modules, which, when executed, may perform corresponding functions.

For example, a first acquisition module, a second acquisition module, a determination module, a recovery module, a first acquisition submodule, a second acquisition submodule, a third acquisition submodule, a fourth acquisition submodule, a fifth acquisition submodule, a sixth acquisition submodule, a first fluctuation value determination submodule, a second fluctuation value determination submodule, a third fluctuation value determination submodule, a fourth fluctuation value determination submodule, a first recovery condition determination submodule, a fifth fluctuation value determination submodule, a second recovery condition determination submodule, a first release submodule, a second release submodule, a first recovery condition determination unit, a second recovery condition determination unit, a third recovery condition determination unit, a fourth recovery condition determination unit, a fifth recovery condition determination unit, a sixth recovery condition determination unit, and a seventh recovery condition determination unit may be implemented by being combined in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module, the second acquisition module, the determination module, the recovery module, the first acquisition sub-module, the second acquisition sub-module, the third acquisition sub-module, the fourth acquisition sub-module, the fifth acquisition sub-module, the sixth acquisition sub-module, the first fluctuation value determination sub-module, the second fluctuation value determination sub-module, the third fluctuation value determination sub-module, the fourth fluctuation value determination sub-module, the first recovery condition determination sub-module, the fifth fluctuation value determination sub-module, the second recovery condition determination sub-module, the first release sub-module, the second release sub-module, the first recovery condition determination unit, the second recovery condition determination unit, the third recovery condition determination unit, the fourth recovery condition determination unit, the fifth recovery condition determination unit, the sixth recovery condition determination unit, and the seventh recovery condition determination unit may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of or any suitable combination of software, hardware, and firmware. Or, at least one of the first acquisition module, the second acquisition module, the determination module, the recovery module, the first acquisition submodule, the second acquisition submodule, the third acquisition submodule, the fourth acquisition submodule, the fifth acquisition submodule, the sixth acquisition submodule, the first fluctuation value determination submodule, the second fluctuation value determination submodule, the third fluctuation value determination submodule, the fourth fluctuation value determination submodule, the first recovery condition determination submodule, the fifth fluctuation value determination submodule, the second recovery condition determination submodule, the first release submodule, the second release submodule, the first recovery condition determination unit, the second recovery condition determination unit, the third recovery condition determination unit, the fourth recovery condition determination unit, the fifth recovery condition determination unit, the sixth recovery condition determination unit, and the seventh recovery condition determination unit may be at least partially implemented as a computer program module, when the computer program modules are run, corresponding functions may be performed.

Fig. 6 schematically illustrates a schematic diagram of a computer-readable storage medium product adapted to implement the above-described method of resource reclamation for containers according to an embodiment of the present disclosure.

In some possible embodiments, aspects of the present invention may also be implemented in the form of a program product including program code for causing a device to perform the aforementioned operations (or steps) in the method for reclaiming resources for a container according to various exemplary embodiments of the present invention described in the aforementioned "exemplary method" section of this specification, when the program product is run on the device. For example, the electronic device may perform operations S210 to S240 as shown in fig. 2. The electronic device may also perform operations S311, S312, S321, S322, S323, and S330 as shown in fig. 3. The electronic device may also perform operations S410 through S490 as shown in fig. 4.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

As shown in fig. 6, a program product 600 for a method of resource reclamation for containers according to an embodiment of the present invention is depicted, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a device, such as a personal computer. However, the program product of the present invention is not limited in this respect, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device. Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAA) or a wide area network (WAA), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Fig. 7 schematically shows a block diagram of an electronic device adapted to implement the above described method of resource reclamation for containers according to an embodiment of the present disclosure. The electronic device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 7, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. The processor 701 may include, for example, a general purpose microprocessor (e.g., a CNU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 701 may also include on-board memory for caching purposes. The processor 701 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 703, various programs and data necessary for the operation of the electronic apparatus 700 are stored. The processor 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. The processor 701 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 702 and/or the RAM 703. It is noted that the programs may also be stored in one or more memories other than the ROM 702 and RAM 703. The processor 701 may also perform operations S210 to S240 shown in fig. 2 according to the embodiment of the present disclosure by executing the program stored in the one or more memories, or may also perform operations S311, S312, S321, S322, S323, and S330 shown in fig. 3, or may also perform operations S410 to S490 shown in fig. 4.

Electronic device 700 may also include input/output (I/O) interface 705, which input/output (I/O) interface 705 is also connected to bus 704, according to an embodiment of the present disclosure. The system 700 may also include one or more of the following components connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as an LAA card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program, when executed by the processor 701, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The above-mentioned computer-readable storage medium carries one or more programs which, when executed, implement a resource reclamation method for containers according to an embodiment of the present disclosure, including operations S210 to S240 shown in fig. 2. The electronic device may also perform operations S311, S312, S321, S322, S323, and S330 as shown in fig. 3, or may also perform operations S410 to S490 as shown in fig. 4.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 702 and/or the RAM 703 and/or one or more memories other than the ROM 702 and the RAM 703 described above.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A resource reclamation method for a container, comprising:

acquiring performance index data of a target container, wherein the performance index data is used for representing the resource use condition of the target container, and the target container provides computing resources for an application program running in the target container;

acquiring running environment data of the target container, wherein the running scene is used for representing a hardware running environment and a software running environment of the target container;

determining whether the target container meets a resource recovery condition based on a statistical result of the performance index data and/or the operation scene data;

and if the resource recovery condition is met, recovering the resources of the target container.

2. The method of claim 1, wherein the collecting performance metric data for a target container comprises:

acquiring first performance index data corresponding to a target container and a processor resource;

acquiring second performance index data corresponding to the target container and the memory resource;

collecting third performance index data corresponding to the target container and the file system resource;

and collecting fourth performance index data corresponding to the target container and the network resource.

3. The method of claim 2, wherein the determining whether the target container satisfies a resource reclamation condition based on the statistics of the performance metric data comprises:

determining a first fluctuation value corresponding to the processor resource based on a statistical result of the first performance indicator data in a first statistical period;

determining a second fluctuation value corresponding to the memory resource based on a statistical result of the second performance index data in a second statistical period;

determining a third fluctuation value corresponding to the file system resource based on a statistical result of the third performance index data in a third statistical period;

determining a fourth fluctuation value corresponding to the network resource based on a statistical result of the fourth performance index data in a fourth statistical period;

determining whether the target container satisfies a resource recovery condition based on the first fluctuation value, the second fluctuation value, the third fluctuation value, and the fourth fluctuation value,

the first statistical period, the second statistical period, the third statistical period and the fourth statistical period may be the same or different.

4. The method of claim 3, wherein the determining whether the target container satisfies a resource reclamation condition based on the first, second, third, and fourth fluctuation values comprises:

determining that the processor resource satisfies a resource reclamation condition if the first fluctuation value is less than a first threshold;

determining that the memory resource meets a resource recovery condition under the condition that the second fluctuation value is smaller than a second threshold value;

determining that the file system resource meets a resource recovery condition under the condition that the third fluctuation value is smaller than a third threshold value;

determining that the network resource meets a resource recovery condition under the condition that the fourth fluctuation value is smaller than a fourth threshold value;

determining whether the target container satisfies a resource reclamation condition if at least two of the processor resource, the memory resource, the file system resource, and the network resource satisfy the resource reclamation condition,

the first threshold, the second threshold, the third threshold, and the fourth threshold may be the same or different.

5. The method of claim 1, wherein the collecting operating environment data for the target container comprises:

collecting log data corresponding to the target container and the log indexes;

acquiring version data of the target container, wherein the version data is used for representing version information of the application program.

6. The method of claim 5, wherein the determining whether the target container satisfies a resource reclamation condition based on the statistics of the operational scenario data comprises:

determining a fifth fluctuation value corresponding to the log index based on a statistical result of the log data in a fifth statistical period;

determining whether the target container satisfies a resource reclamation condition based on the fifth fluctuation value and the version data,

the fifth statistical period may be the same as or different from the first statistical period, the second statistical period, the third statistical period, and the fourth statistical period.

7. The method of claim 6, wherein the determining whether the target container satisfies a resource reclamation condition based on the fifth fluctuation value and the version data comprises:

determining that the target container satisfies a resource recovery condition if the fifth fluctuation value is less than a fifth threshold;

determining that the target container satisfies a resource reclamation condition if the version data representation is inconsistent with version information of the application,

the fifth threshold may be the same as or different from the first threshold, the second threshold, the third threshold, and the fourth threshold.

8. The method of claim 1, wherein the reclaiming resources of the target container comprises:

according to the recycling priority, releasing processor resources and memory resources occupied by the target container;

and releasing the occupation of the file system resources by the target container under the condition that the occupation of the file system resources exceeds the preset time length.

9. A asset retrieval device for a container, comprising:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring performance index data of a target container, the performance index data is used for representing the resource use condition of the target container, and the target container provides computing resources for an application program running in the target container;

the second acquisition module is used for acquiring the operating environment data of the target container, wherein the operating scene is used for representing the hardware operating environment and the software operating environment of the target container;

a determining module, configured to determine whether the target container meets a resource recovery condition based on a statistical result of the performance indicator data and/or the operation scenario data;

and the recovery module is used for recovering the resources of the target container if the resource recovery condition is met.

10. An electronic device, comprising:

one or more processors; and

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.

11. A computer-readable storage medium storing computer-executable instructions that, when executed, cause a processor to perform the method of any one of claims 1 to 8.

12. A computer program product comprising a computer program which, when executed by a processor, performs the method according to any one of claims 1 to 8.