CN111752676A - Docker-based homonymous mirror image removing method, system, terminal and storage medium - Google Patents
Docker-based homonymous mirror image removing method, system, terminal and storage medium Download PDFInfo
- Publication number
- CN111752676A CN111752676A CN202010471021.7A CN202010471021A CN111752676A CN 111752676 A CN111752676 A CN 111752676A CN 202010471021 A CN202010471021 A CN 202010471021A CN 111752676 A CN111752676 A CN 111752676A
- Authority
- CN
- China
- Prior art keywords
- mirror image
- original
- image
- docker
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 230000008569 process Effects 0.000 claims abstract description 38
- 238000012544 monitoring process Methods 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 4
- 241000109539 Conchita Species 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Abstract
The invention provides a method, a system, a terminal and a storage medium for removing a homonymous mirror image based on Docker, wherein the method comprises the following steps: before creating a target mirror image, searching an original mirror image with the same name as the target mirror image; marking the original mirror image and monitoring the address of the original mirror image; and monitoring the creation process or the pulling process of the target mirror image, and deleting the original mirror image at the current address of the original mirror image after the completion of the creation process or the pulling process of the target mirror image is monitored. The invention strengthens the function of Docker for clearing invalid images by automatically clearing the old images with the same name, thereby avoiding the possibility of service interruption caused by the continuous increase of the utilization rate of a disk after a new image is created or pulled to occupy a large amount of storage space; the generation of < none > "mirror image is avoided, and the safe and reliable operation of the application is guaranteed; meanwhile, the complexity of manual operation and maintenance is reduced, and the maintenance cost is reduced.
Description
Technical Field
The invention belongs to the technical field of servers, and particularly relates to a method, a system, a terminal and a storage medium for removing a homonymous mirror image based on Docker.
Background
When a Docker mirror image is built and an application is deployed every day by a CI/CD, a new mirror image is created or pulled, and an old mirror image cannot be automatically deleted, so that the utilization rate of a disk is continuously increased to occupy a large amount of storage space, automatic clearing needs to be set during mirror image construction and pulling, and the risk of full disk service interruption is avoided.
However, when the old mirror image is deleted, once the creation process or the pull process of the new mirror image is not completed, the mirror image cache is already cleared, so that the progress of the creation process or the pull process of the new mirror image is greatly reduced, and time is seriously wasted. Therefore, how to timely delete the old mirror image is a technical problem which needs to be solved urgently.
Disclosure of Invention
In view of the above deficiencies in the prior art, the present invention provides a method, a system, a terminal and a storage medium for removing a homonymous mirror image based on Docker, so as to solve the above technical problems.
In a first aspect, the present invention provides a method for removing a homonymous mirror image based on Docker, including:
before creating a target mirror image, searching an original mirror image with the same name as the target mirror image;
marking the original mirror image and monitoring the address of the original mirror image;
and monitoring the creation process or the pulling process of the target mirror image, and deleting the original mirror image at the current address of the original mirror image after the completion of the creation process or the pulling process of the target mirror image is monitored.
Further, the searching for the original mirror image with the same name as the target mirror image includes:
and obtaining mirror names and labels from the docker pull or docker build command line, and then searching the original mirror globally according to the mirror names and labels.
Further, the marking an original mirror image and monitoring an address of the original mirror image includes:
setting a monitoring period;
and periodically searching the original mirror image in a memory according to the monitoring period, and updating the address of the searched original mirror image.
Further, before deleting the original image, the method further includes:
and searching the related container started by the original mirror image and deleting the related container.
In a second aspect, the present invention provides a system for removing a mirror image of the same name based on Docker, including:
the mirror image control unit is configured to search an original mirror image with the same name as the target mirror image before creating the target mirror image;
the mirror image monitoring unit is configured to mark the original mirror image and monitor the address of the original mirror image;
and the mirror image deleting unit is configured to monitor a creating process or a pulling process of the target mirror image, and delete the original mirror image at the current address of the original mirror image after the monitoring of the creating process or the pulling process of the target mirror image is finished.
Further, the mirroring control unit includes:
and the searching module is configured to obtain the mirror image name and the label from the docker pull or docker built command line, and then search the original mirror image globally according to the mirror image name and the label.
Further, the image monitoring unit includes:
a period setting module configured to set a monitoring period;
and the path updating module is configured to periodically search the original mirror image in the memory according to the monitoring period and update the address of the searched original mirror image.
Further, the system comprises:
and the container deleting unit is configured to search the related container of which the original mirror image is started and delete the related container.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is used for calling and running the computer program from the memory so as to make the terminal execute the method of the terminal.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
according to the Docker-based homonymous mirror image clearing method, the system, the terminal and the storage medium, the function of clearing invalid mirror images by Docker is enhanced by automatically clearing homonymous old mirror images, and the possibility of service interruption caused by the fact that the utilization rate of a disk continuously increases and occupies a large amount of storage space after a new mirror image is created or pulled is avoided; the generation of < none > "mirror image is avoided, and the safe and reliable operation of the application is guaranteed; meanwhile, the complexity of manual operation and maintenance is reduced, and the maintenance cost is reduced.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 3 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be a system for removing a mirror image of the same name based on Docker.
As shown in fig. 1, the method 100 includes:
In order to facilitate understanding of the present invention, the principle of the method for removing the homonymous mirror image based on Docker of the present invention is combined with the process of removing the homonymous mirror image based on Docker in the embodiment, so as to further describe the method for removing the homonymous mirror image based on Docker of the present invention.
Referring to fig. 2, in detail, the method for removing the same-name image based on Docker includes:
s1, before creating the target image, the original image with the same name as the target image is searched.
When the mirror IMAGE controller with the same name is used for making a mirror IMAGE and pulling the mirror IMAGE, the mirror IMAGE controller with the same name finds the mirror IMAGE with the same name, sends an IMAGE ID to a mirror IMAGE memory with the same name, monitors a mirror IMAGE making and pulling ending mark, and finally sends a request to a remover for deleting the mirror IMAGE with the same name according to the IAMGE ID;
IMAGE NAME and TAG are obtained from the docker pull or docker build command line and then globally looked up according to IMAGE NAME and TAG, for example: docker pull centros latest, then centros (IMAGENAME), latest (TAG)
The found ID is then put into the channel, for example: old _ centros _ latest ═ b6a3fd7766e7dd2d507e1a1d752b00a68d94b492da8c3f53a548f56bc8ee9aa4
Monitoring the end marks of the docker budild and the docker pull, and issuing a command to the image deleter with the same name, such as: latest, image (centros)
And S2, marking the original mirror image and monitoring the address of the original mirror image.
After receiving the IMAGE ID of the IMAGE making controller, the IMAGE memory with the same name stores the IMAGE ID locally, then continuously searches for a local IMAGE according to local storage information, and if the local storage IMAGE ID is found to be changed, the local storage IMAGE ID is updated in time;
obtaining the IMAGE ID from the channel, for example: old _ centros _ latest ═ b6a3fd7766e7dd2d507e1a1d752b00a68d94b492da8c3f53a548f56bc8ee9aa4
Persisting the value locally, looking up the local mirror IMAGE through IMAGE ID period, if there is a change found, self-learning, for example: old _ centros _ latest ═ b6a3fd7766e7dd2d507e1a1d752b00a68d94b492da8c3f53a548f56bc8ee9aa4 was changed to old _ centros _ latest ═ c7a3fd7766e7dd2d507e1a1d752b00a68d94b 8c3f53a548f56bc8ee9aad
A query operation is provided and the value is deleted after the result is returned.
S3, monitoring the creation process or the pull process of the target mirror image, and deleting the original mirror image at the current address of the original mirror image after the completion of the monitored creation process or the pull process of the target mirror image.
After receiving the request of the controller, the IMAGE deleter with the same name requests the IMAGE memory with the same name for the old IMAGE ID, searches the started container according to the IMAGE ID, executes the operation of deleting the container, and finally executes the operation of deleting the IMAGE;
after receiving the mirror controller command with the same name, according to IMAGE NAME and TAG, the old IMAGE ID is looked up from the mirror memory with the same name, for example: centos-latest- > b6a3fd7766e7dd2d507e1a1d752b00a68d94b492da8c3f53a548f56bc8ee9aa4
Finding the started CONTAINER according to the IMAGE ID, and deleting the CONTAINER according to the CONTAINER ID, for example: docker rm-fb492da8c3f53a548f56bc8ee9aa4cb6a3fd7766e7dd2d507e1a1d752b00a68d9
Deleting the image according to the ID, for example: docker rmi-fb6a3fd7766e7dd2d507e1a1d752b00a68d94b492da8c3f53a548f56bc8ee9aa4
As shown in fig. 3, the system 300 includes:
a mirror image control unit 310 configured to search for an original mirror image having the same name as a target mirror image before creating the target mirror image;
a mirror monitoring unit 320 configured to mark the original mirror and monitor an address of the original mirror;
and the mirror image deleting unit 330 is configured to monitor a creating process or a pulling process of the target mirror image, and delete the original mirror image at the current address of the original mirror image after the monitoring of the creating process or the pulling process of the target mirror image is finished.
Optionally, as an embodiment of the present invention, the mirroring control unit includes:
and the searching module is configured to obtain the mirror image name and the label from the docker pull or docker built command line, and then search the original mirror image globally according to the mirror image name and the label.
Optionally, as an embodiment of the present invention, the mirror image monitoring unit includes:
a period setting module configured to set a monitoring period;
and the path updating module is configured to periodically search the original mirror image in the memory according to the monitoring period and update the address of the searched original mirror image.
Optionally, as an embodiment of the present invention, the system includes:
and the container deleting unit is configured to search the related container of which the original mirror image is started and delete the related container.
Fig. 4 is a schematic structural diagram of a terminal system 400 according to an embodiment of the present invention, where the terminal system 400 may be configured to execute a method for removing a mirror image under the same name based on Docker according to the embodiment of the present invention.
The terminal system 400 may include: a processor 410, a memory 420, and a communication unit 430. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 420 may be used for storing instructions executed by the processor 410, and the memory 420 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 420, when executed by processor 410, enable terminal 400 to perform some or all of the steps in the method embodiments described below.
The processor 410 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 420 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 410 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 430, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description in the method embodiment.
In the embodiments provided in the present invention, it should be understood that the disclosed system and method can be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for removing a homonymous mirror image based on Docker is characterized by comprising the following steps:
before creating a target mirror image, searching an original mirror image with the same name as the target mirror image;
marking the original mirror image and monitoring the address of the original mirror image;
and monitoring the creation process or the pulling process of the target mirror image, and deleting the original mirror image at the current address of the original mirror image after the completion of the creation process or the pulling process of the target mirror image is monitored.
2. The method of claim 1, wherein the finding the original image with the same name as the target image comprises:
and obtaining mirror names and labels from the docker pull or docker build command line, and then searching the original mirror globally according to the mirror names and labels.
3. The method of claim 1, wherein marking the original image and monitoring an address of the original image comprises:
setting a monitoring period;
and periodically searching the original mirror image in a memory according to the monitoring period, and updating the address of the searched original mirror image.
4. The method of claim 1, wherein prior to the deleting the original image, the method further comprises:
and searching the related container started by the original mirror image and deleting the related container.
5. A system for removing a homonymous image based on Docker, comprising:
the mirror image control unit is configured to search an original mirror image with the same name as the target mirror image before creating the target mirror image;
the mirror image monitoring unit is configured to mark the original mirror image and monitor the address of the original mirror image;
and the mirror image deleting unit is configured to monitor a creating process or a pulling process of the target mirror image, and delete the original mirror image at the current address of the original mirror image after the monitoring of the creating process or the pulling process of the target mirror image is finished.
6. The system of claim 5, wherein the mirroring control unit comprises:
and the searching module is configured to obtain the mirror image name and the label from the docker pull or docker built command line, and then search the original mirror image globally according to the mirror image name and the label.
7. The system of claim 5, wherein the mirror monitoring unit comprises:
a period setting module configured to set a monitoring period;
and the path updating module is configured to periodically search the original mirror image in the memory according to the monitoring period and update the address of the searched original mirror image.
8. The system of claim 5, wherein the system comprises:
and the container deleting unit is configured to search the related container of which the original mirror image is started and delete the related container.
9. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any one of claims 1-4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010471021.7A CN111752676B (en) | 2020-05-28 | 2020-05-28 | Docker-based homonymous mirror image removing method, system, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010471021.7A CN111752676B (en) | 2020-05-28 | 2020-05-28 | Docker-based homonymous mirror image removing method, system, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111752676A true CN111752676A (en) | 2020-10-09 |
| CN111752676B CN111752676B (en) | 2022-06-21 |
Family
ID=72674100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010471021.7A Active CN111752676B (en) | 2020-05-28 | 2020-05-28 | Docker-based homonymous mirror image removing method, system, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111752676B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117246A (en) * | 2015-08-04 | 2015-12-02 | 晶晨半导体(上海)有限公司 | Method for rapidly booting electronic equipment |
| US9639558B2 (en) * | 2015-09-17 | 2017-05-02 | International Business Machines Corporation | Image building |
| CN106997392A (en) * | 2017-04-10 | 2017-08-01 | 北京搜狐新媒体信息技术有限公司 | Processing method, device and the read method and device of Docker mirror cache information |
| CN107066296A (en) * | 2017-03-31 | 2017-08-18 | 北京奇艺世纪科技有限公司 | The method for cleaning and device of mirror image in a kind of clustered node |
| CN107463467A (en) * | 2017-08-24 | 2017-12-12 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system that can quickly reduce virtual platform |
| US10248661B2 (en) * | 2015-10-28 | 2019-04-02 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method and device for pulling virtual machine mirror file |
| CN109656631A (en) * | 2017-10-11 | 2019-04-19 | 北京国双科技有限公司 | Service arrangement method and device |
| CN110442480A (en) * | 2019-07-31 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of mirror image data method for cleaning, apparatus and system |
| CN111124612A (en) * | 2019-12-20 | 2020-05-08 | 北京浪潮数据技术有限公司 | Container mirror image upgrading method and device, electronic equipment and storage medium |
-
2020
- 2020-05-28 CN CN202010471021.7A patent/CN111752676B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117246A (en) * | 2015-08-04 | 2015-12-02 | 晶晨半导体(上海)有限公司 | Method for rapidly booting electronic equipment |
| US9639558B2 (en) * | 2015-09-17 | 2017-05-02 | International Business Machines Corporation | Image building |
| US10248661B2 (en) * | 2015-10-28 | 2019-04-02 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method and device for pulling virtual machine mirror file |
| CN107066296A (en) * | 2017-03-31 | 2017-08-18 | 北京奇艺世纪科技有限公司 | The method for cleaning and device of mirror image in a kind of clustered node |
| CN106997392A (en) * | 2017-04-10 | 2017-08-01 | 北京搜狐新媒体信息技术有限公司 | Processing method, device and the read method and device of Docker mirror cache information |
| CN107463467A (en) * | 2017-08-24 | 2017-12-12 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system that can quickly reduce virtual platform |
| CN109656631A (en) * | 2017-10-11 | 2019-04-19 | 北京国双科技有限公司 | Service arrangement method and device |
| CN110442480A (en) * | 2019-07-31 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of mirror image data method for cleaning, apparatus and system |
| CN111124612A (en) * | 2019-12-20 | 2020-05-08 | 北京浪潮数据技术有限公司 | Container mirror image upgrading method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111752676B (en) | 2022-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102246152B (en) | Saving program execution state | |
| CN102779185B (en) | High-availability distribution type full-text index method | |
| CN102882909B (en) | Cloud computing service monitoring system and method thereof | |
| CN112260876A (en) | Dynamic gateway route configuration method, platform, computer equipment and storage medium | |
| CN109656742B (en) | Node exception handling method and device and storage medium | |
| CN109976949B (en) | BMC fault mirror image rollback refreshing method, device, terminal and storage medium | |
| CN112256401B (en) | Prometheus high-availability system based on Kubernetes environment and implementation method | |
| CN103716384A (en) | Method and device for realizing cloud storage data synchronization in cross-data-center manner | |
| CN113037771A (en) | Method and device for controlling device shadow, storage medium and electronic device | |
| CN111147560B (en) | Data synchronization method based on HTTP (hyper text transport protocol) and breakpoint continuous transmission | |
| CN111752676B (en) | Docker-based homonymous mirror image removing method, system, terminal and storage medium | |
| CN113271359A (en) | Method and device for refreshing cache data, electronic equipment and storage medium | |
| CN111353772B (en) | Single number generation method and device, storage medium and electronic device | |
| CN111752861A (en) | Application multi-level caching method and device, client and storage medium | |
| CN110196749A (en) | The restoration methods and device of virtual machine, storage medium and electronic device | |
| CN113031992B (en) | Annoy hot update method, device, equipment and medium | |
| CN104536784B (en) | Real-time system update method and device | |
| CN110554992B (en) | Distributed metadata path management method, system, terminal and storage medium | |
| CN114398381A (en) | Diagnosis and treatment data processing method and device | |
| CN112463399A (en) | Server BMC information management method, system, terminal and storage medium | |
| CN102799996A (en) | Network advertisement strategy matching method and system | |
| JP2000184595A (en) | Display drawing generation management system and storage medium for recording processing program thereof | |
| CN115185921B (en) | Database fault loss stopping method, device, electronic equipment, medium and program product | |
| CN111817895B (en) | Master control node switching method, device, equipment and storage medium | |
| CN117743297A (en) | Serverless-based mysql stateful storage elastic expansion and contraction method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |