CN112434008A - Distributed database upgrading method, device and medium - Google Patents

Distributed database upgrading method, device and medium Download PDF

Info

Publication number
CN112434008A
CN112434008A CN202011295446.3A CN202011295446A CN112434008A CN 112434008 A CN112434008 A CN 112434008A CN 202011295446 A CN202011295446 A CN 202011295446A CN 112434008 A CN112434008 A CN 112434008A
Authority
CN
China
Prior art keywords
container
management controller
upgrading
container management
node
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.)
Pending
Application number
CN202011295446.3A
Other languages
Chinese (zh)
Inventor
舒锦
边雨
刘汪根
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Transwarp Technology Shanghai Co Ltd
Original Assignee
Transwarp Technology Shanghai Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Transwarp Technology Shanghai Co Ltd filed Critical Transwarp Technology Shanghai Co Ltd
Priority to CN202011295446.3A priority Critical patent/CN112434008A/en
Publication of CN112434008A publication Critical patent/CN112434008A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Abstract

The embodiment of the invention discloses a distributed database upgrading method, equipment and a medium. The method comprises the following steps: updating the upgrading configuration information of the first container management controller corresponding to all the main storage nodes according to the upgrading information in the upgrading request; when the containers in the main storage nodes are detected to be upgraded, updating the upgrading configuration information of the second container management controller corresponding to all the backup storage nodes according to the upgrading information; when the containers in the backup storage nodes are detected to be upgraded, updating the upgrading configuration information of the third container management controller corresponding to the computing node according to the upgrading information; and when the containers in the computing nodes are detected to be upgraded, updating the upgrading configuration information of the fourth container management controller corresponding to the proxy server according to the upgrading information. The embodiment of the invention can automatically finish the upgrading process of the distributed database on the premise of uninterrupted service.

Description

Distributed database upgrading method, device and medium
Technical Field
The embodiment of the invention relates to the technical field of databases, in particular to a distributed database upgrading method, equipment and a medium.
Background
Distributed databases are increasingly used in industries such as industry, finance and the like, and become the mainstream of next generation databases. The distributed database can realize large-capacity and multi-class data storage, and can provide high-concurrency and high-performance data access service to the outside through cooperative work among a plurality of database devices. Because distributed databases generally involve multiple nodes and multiple roles, performance can be improved, but the upgrading work of the databases is also complicated and risky.
In the related art, a shell script is usually adopted to deploy a distributed database, and the shell script is executed to upgrade the distributed database. In the upgrading process, the process start and stop control is carried out by complex shell scripts which need to be compiled in advance, if the number of related nodes is large, the upgrading process is extremely complex, errors are easy to occur, rolling upgrading cannot be guaranteed, and service interruption can be caused.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, and a medium for upgrading a distributed database, so as to automatically complete an upgrading process of the distributed database without service interruption.
In a first aspect, an embodiment of the present invention provides a distributed database upgrading method, including:
updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information;
when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information;
when the fact that the containers in the backup storage nodes are upgraded is detected, updating upgrading configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information;
when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information;
wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
In a second aspect, embodiments of the present invention also provide a computer device, including a processor and a memory, the memory storing instructions that, when executed, cause the processor to:
updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information;
when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information;
when the fact that the containers in the backup storage nodes are upgraded is detected, updating a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information;
when the fact that the container in the computing node is upgraded is detected, updating a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information;
wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
In a third aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements:
updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information;
when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information;
when the fact that the containers in the backup storage nodes are upgraded is detected, updating a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information;
when the fact that the container in the computing node is upgraded is detected, updating a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information;
wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
According to the technical scheme of the embodiment of the invention, the distributed database is deployed on the basis of a Kubernets container platform, the main storage nodes, the backup storage nodes, the computing nodes and the proxy server in the distributed database are subjected to rolling upgrade according to a set sequence through the container management controllers respectively corresponding to the main storage nodes, the backup storage nodes, the computing nodes and the proxy server, so that automatic rolling upgrade of all types of nodes in the distributed database is realized, online services are not influenced in the rolling upgrade process, service is not performed discontinuously, manual intervention is not required in the rolling upgrade process, the online upgrade operation is extremely simple, and the operation and maintenance personnel only need one upgrade request to realize automatic rolling upgrade of all types of nodes in the distributed database.
Drawings
Fig. 1A is a schematic diagram of an overall architecture of a distributed database according to an embodiment of the present invention.
Fig. 1B is a flowchart of a distributed database upgrading method according to an embodiment of the present invention.
Fig. 2 is a flowchart of a distributed database upgrading method according to a second embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a distributed database upgrading apparatus according to a third embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The term "kubernets container platform" as used herein is a container cluster management system of google open sources. A distributed database is deployed based on a Kubernets container platform, and services and workloads can be operated by a plurality of variable containers (pods) on each node in the distributed database. Each container is isolated from each other, so that the safety of the running process can be ensured. The container isolates different processes running on the nodes through a virtualization technology, so that the processes, the processes and a host operating system are isolated from each other and do not influence each other. The mutually isolated processes are called containers, and each container has a set of file system resources and a set of subordinate processes.
The term "master storage node" (master node) as used herein is a node in a distributed database that provides read-write services. The term "backup storage node" (slave node) as used herein is a node in a distributed database that synchronizes data of primary storage nodes for backup. Each main storage node corresponds to at least one backup storage node. The main storage node is used for providing read-write service, and the backup storage node corresponding to the main storage node is used for synchronizing the data of the main storage node for backup.
The term "computing node" (ComputeNode) as used herein is a node in a distributed database for handling complex computing traffic.
The term "proxy server" (proxy) as used herein is a node in a distributed database for providing connection services to the outside, and is responsible for access and Structured Query Language (SQL) compilation, SQL routing, and the like.
The distributed database mainly comprises three parts: a proxy server (proxy) that mainly provides connection services to the outside, a computing node (ComputeNode) that is mainly responsible for complex computing services, and a storage section. The storage part is mainly a multi-segment main and standby structure: the main storage node is used for providing read-write service, and the backup storage node corresponding to the main storage node is used for synchronizing the data of the main storage node for backup.
Fig. 1A is a schematic diagram of an overall architecture of a distributed database according to an embodiment of the present invention. As shown in fig. 1A, the distributed database includes: a proxy server 11, a compute node 12, and a storage section. The storage section includes: a first primary storage node 13, a first backup storage node 14 and a second backup storage node 15 corresponding to the first primary storage node 13, a second primary storage node 16, a third backup storage node 17 and a fourth backup storage node 18 corresponding to the second primary storage node 16.
The term "container hosting controller" (replitionset controller) as used herein is a component in the kubernets container platform for controlling containers, which can create containers, delete containers. The container hosting controller records the configuration index file (PodSpec) of the container by means of a markup language YAML declaration. The configuration index file of the container describes the version of the container use image, the mounting directory of the configuration file, the resources and environment variables of the use machine and the like. The number of pods that the container tote controller can ensure run: ensuring that a specified number of containers are in operation. If the number of the containers in operation is less than the specified number, the container hosting controller creates a new container; if the number of containers in operation is greater than the specified number, the container hosting controller will delete the excess containers to ensure that the specified number of containers are in operation. The vessel tote controller can ensure vessel health: when a container is unhealthy, e.g., a container is running in error or cannot be serviced, the container hosting controller may delete the unhealthy container and recreate a new container.
The term "container management controller" (Deployment controller) as used herein is a component in the kubernets container platform for managing and maintaining container pallet controllers and containers hosted in container pallet controllers. One container management controller (depolyment controller) can manage a plurality of container hosting controllers (ReplicationSet controllers). The container management controller can create a container hosting controller, and can set container configuration information of the container hosting controller in a declaration manner to control the number of containers hosted in the container hosting controller. Each operation on the container management controller can be saved and can be used for subsequent possible rollback.
The term "first container management controller" as used herein is a container management controller for managing at least one container hosting controller responsible for controlling containers in a master storage node. And allocating the container in each main storage node to at least one container hosting controller, and controlling the container in the allocated main storage node by the container hosting controller. Each currently-running container hosting controller corresponding to the first container management controller is the container hosting controller which is running at the current time and is responsible for controlling the containers in the main storage node.
The term "second container management controller" as used herein is a container management controller for managing at least one container hosting controller responsible for controlling containers in the backup storage node. And allocating the containers in each backup storage node to at least one container hosting controller, and controlling the containers in the allocated backup storage nodes by the container hosting controllers. Each currently-operating container hosting controller corresponding to the second container management controller is the container hosting controller which is operating at the current time and is responsible for controlling the containers in the backup storage node.
The term "third container management controller" as used herein is a container management controller for managing a container hosting controller responsible for controlling containers in a compute node. The containers in the compute nodes are assigned to a container hosting controller, which controls the containers in the compute nodes. The currently-operating container hosting controller corresponding to the third container management controller is the container hosting controller which is operating at the current time and is responsible for controlling the containers in the computing nodes.
The term "fourth container management controller" as used herein is a container management controller for managing a container hosting controller responsible for controlling containers in the proxy server. The container in the proxy server is assigned to a container hosting controller, which controls the container in the proxy server. The currently-operating container hosting controller corresponding to the third container management controller is the container hosting controller which is operating at the current time and is responsible for controlling the containers in the computing nodes.
The term "upgrade request" as used herein is a request for an upgrade to a distributed database. The upgrade request carries upgrade information.
The term "upgrade information" as used herein is information used to control the upgrade of a distributed database and may include the version identification and storage address of the new version image. An image is a file used to create a container. The image can comprise executable files, dependent software, library files, configuration files and the like required by the operation of the container. The new version image is a file used to create the new version container. The new version image can comprise executable files, dependent software, library files, configuration files and the like required by the operation of the new version container. The new version image and the image to which the container in the running state in the distributed database belongs are images of different versions. The version identification is identification information for distinguishing images of different versions. The storage address is the storage location of the new version image.
The term "upgrade configuration information" used herein is information for upgrading a container controlled by a container hosting controller managed by a container management controller, and may include a version identification and a storage address of a new version image. And after detecting that the upgrade configuration information is updated, the container management controller performs rolling upgrade on the containers controlled by the managed container hosting controller according to the updated upgrade configuration information, and upgrades all the containers controlled by the managed container hosting controller into new version containers.
The term "node upgrade order" as used herein is an upgrade order in which a primary storage node is upgraded first, then a backup storage node is upgraded, then a compute node is upgraded, and finally a proxy server is upgraded.
The term "upgraded node" as used herein is a node where a container has been upgraded to a new version of the container.
The term "rollback instruction" as used herein is an instruction for controlling a container management controller to rollback a container controlled by a container hosting controller managed by the container management controller to a pre-upgrade version.
The term "upgrade record information" used herein is information related to each upgrade process recorded by the container management controller, and may include a version identification and a storage address of a new version image corresponding to each upgrade process.
The term "currently operating container tote controller" as used herein is a container tote controller that is operating at the current time.
The term "currently running container" as used herein is a container that is running at the current time.
The term "container configuration information" as used herein is information used to upgrade a container controlled by a container hosting controller and may include a version identification and a storage address of a new version image.
The term "configuration information of a container" as used herein is information required by the container at runtime, and may include at least one of container operation information, container storage information, and container environment variables. The container operation information is an operation state record generated in the operation process of the container. The container storage information is a storage location, a storage address, and the like of the container. The configuration information of the container may further include a mount path, a distribution port, process scheduling information, functional service information, and the like of the container.
For ease of understanding, the main inventive concepts of the embodiments of the present invention are briefly described.
In the related art, a shell script is usually adopted to deploy a distributed database, and the shell script is executed to upgrade the distributed database. In the upgrading process, the process start and stop control is carried out by complex shell scripts which need to be compiled in advance, if the number of related nodes is large, the upgrading process is extremely complex, errors are easy to occur, rolling upgrading cannot be guaranteed, and service interruption can be caused. It is also quite complicated to roll back if there is an error in the upgrade process.
The inventor considers whether the upgrading process can be automatically completed by a method or not and can solve the problems of service interruption and rollback in the upgrading process aiming at the problems that the upgrading process in the related technology is possibly abnormally complex, is easy to make mistakes and cannot ensure rolling upgrading, and can cause service interruption, and if the upgrading process is made mistakes, rollback is also quite complex, so that lossless switching is really realized.
Based on the above thought, the inventor creatively proposes that the upgrade configuration information of the first container management controller corresponding to all the main storage nodes in the distributed database is updated according to the upgrade information in the upgrade request, so that the first container management controller performs rolling upgrade on the containers in the main storage nodes according to the updated upgrade configuration information; when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information; when the fact that the containers in the backup storage nodes are upgraded is detected, updating upgrading configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information; when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information; wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server. The method has the advantages that the distributed database is deployed on the basis of the Kubernets container platform, the main storage nodes, the backup storage nodes, the computing nodes and the proxy server in the distributed database are subjected to rolling upgrade through the container management controllers respectively corresponding to the main storage nodes, the backup storage nodes, the computing nodes and the proxy server according to the set sequence, automatic rolling upgrade of all types of nodes in the distributed database is achieved, online services are not affected in the rolling upgrade process, discontinuous service execution is avoided, manual intervention is not needed in the rolling upgrade process, online upgrade operation is extremely simple, and operation and maintenance personnel can achieve automatic rolling upgrade of all types of nodes in the distributed database only through one upgrade request.
Further, when it is detected that any target node in the distributed database fails to be upgraded, controlling the target node and an upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process; the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server. The method has the advantages that automatic rollback can be realized when any step in the upgrading process is wrong, the problems of service interruption and rollback in the upgrading process can be solved, and lossless switching is really realized.
Example one
Fig. 1B is a flowchart of a distributed database upgrading method according to an embodiment of the present invention. The embodiment of the present invention is applicable to upgrading a distributed database, and the method may be executed by the distributed database upgrading apparatus provided in the embodiment of the present invention, and the apparatus may be implemented in a software and/or hardware manner, and may be generally integrated in a computer device. As shown in fig. 1B, the method of the embodiment of the present invention specifically includes:
step 101, updating the upgrade configuration information of the first container management controller corresponding to all the main storage nodes in the distributed database according to the upgrade information in the upgrade request, so that the first container management controller performs rolling upgrade on the containers in each main storage node according to the updated upgrade configuration information.
Wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
Optionally, updating, according to the upgrade information in the upgrade request, the upgrade configuration information of the first container management controller corresponding to all the main storage nodes in the distributed database, including: and setting the version identification and the storage address of the new version image in the upgrading information as the version identification and the storage address of the new version image in the upgrading configuration information of the first container management controller.
Optionally, the performing, by the first container management controller, rolling upgrade on the container in each primary storage node according to the updated upgrade configuration information includes: when the first container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the first container management controller; the system comprises a current operation container management controller, a main storage node and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the main storage node; the first container management controller sets container configuration information of a new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the first container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
Optionally, the currently-operated container is stopped first, and then a new container corresponding to the currently-operated container is operated. In the process, the active-standby switching occurs, and the active-standby switching is the most basic function of the database with high availability, so that the online service is not influenced, and the time is very short.
Thus, the number of the current operation containers managed by each current operation container hosting controller corresponding to the first container management controller is gradually reduced until the number of the current operation containers managed by each current operation container hosting controller corresponding to the first container management controller is 0. And simultaneously, the number of new version containers managed by the new container hosting controller is increased. The first container management controller needs to ensure that the number of the current healthy containers cannot be smaller than the difference between the total number of the currently managed containers and the preset unavailable container threshold value. The preset unavailable container threshold is a maximum number of unavailable containers that the first container management controller may allow to exist.
Optionally, the creating, according to the new version image, a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller includes: a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the main storage node where the target current running container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
Optionally, the YAML script is used to control the process of rolling and upgrading the containers in the main storage nodes by the first container management controller according to the updated upgrade configuration information, and no manual intervention is required.
Optionally, the first container management controller obtains all container hosting controllers managed by the current first container management controller, sequences and finds out the latest container hosting controller, compares the version identifier corresponding to the latest container hosting controller with the version identifier of the new version image in the upgrade configuration information of the first container management controller, and if the version identifiers are not consistent, determines that the upgrade configuration information is updated, and needs to create a new container hosting controller.
Optionally, creating a corresponding new container hosting controller for each currently running container hosting controller corresponding to the first container management controller, including: calculating the hash value of the version identification of the new version image in the upgrade configuration information of the current first container management controller, adding the hash value into the label selectors (label and selector) of the container hosting controller, calculating the maximum version (version) of all the old container management controllers, and adding one to serve as the version (version) of the new container hosting controller.
And 102, when the containers in the main storage nodes are detected to be upgraded, updating the upgrading configuration information of the second container management controller corresponding to all the backup storage nodes in the distributed database according to the upgrading information, so that the second container management controller performs rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information.
Optionally, updating, according to the upgrade information, upgrade configuration information of the second container management controller corresponding to all backup storage nodes in the distributed database, including: and setting the version identification and the storage address of the new version mirror image in the upgrading information as the version identification and the storage address of the new version mirror image in the upgrading configuration information of the second container management controller.
Optionally, the performing, by the second container management controller, rolling upgrade on the container in each backup storage node according to the updated upgrade configuration information includes: when the second container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the second container management controller; the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in a backup storage node; the second container management controller sets the container configuration information of the new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the second container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
Optionally, the currently-operated container is stopped first, and then a new container corresponding to the currently-operated container is operated. In the process, the active-standby switching occurs, and the active-standby switching is the most basic function of the database with high availability, so that the online service is not influenced, and the time is very short.
Thus, the number of the currently-operated containers managed by each currently-operated container hosting controller corresponding to the second container management controller is gradually reduced until the number of the currently-operated containers managed by each currently-operated container hosting controller corresponding to the second container management controller is 0. And simultaneously, the number of new version containers managed by the new container hosting controller is increased. But the second container management controller needs to ensure that the number of the current healthy containers cannot be smaller than the difference between the total number of the currently managed containers and the preset unavailable container threshold. The preset unavailable container threshold is a maximum number of unavailable containers that the second container management controller may allow to exist.
Optionally, the creating, according to the new version image, a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller includes: a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the backup storage node where the target current operation container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
Optionally, the YAML script is used to control the process of rolling and upgrading the containers in each backup storage node by the second container management controller according to the updated upgrade configuration information, and no manual intervention is required.
Optionally, the second container management controller obtains all container hosting controllers managed by the current second container management controller, sequences and finds out the latest container hosting controller, compares the version identifier corresponding to the latest container hosting controller with the version identifier of the new version image in the upgrade configuration information of the second container management controller, and if the version identifiers are not consistent, determines that the upgrade configuration information is updated, and needs to create a new container hosting controller.
Optionally, creating a corresponding new container hosting controller for each currently running container hosting controller corresponding to the second container management controller, including: and calculating the hash value of the version identification of the new version image in the upgrade configuration information of the current second container management controller, adding the hash value into a label selector (label and selector) of the container hosting controller, calculating the maximum version (version) of all the old container management controllers, and adding one to the maximum version (version) to be used as the version (version) of the new container hosting controller.
And 103, when it is detected that the containers in the backup storage nodes are upgraded, updating the upgrade configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrade information, so that the third container management controller performs rolling upgrade on the containers in the computing nodes according to the updated upgrade configuration information.
Optionally, updating, according to the upgrade information, upgrade configuration information of a third container management controller corresponding to a computing node in the distributed database, where the upgrade configuration information includes: and setting the version identification and the storage address of the new version mirror image in the upgrading information as the version identification and the storage address of the new version mirror image in the upgrading configuration information of the third container management controller.
Optionally, the performing, by the third container management controller, rolling upgrade on the container in the computing node according to the updated upgrade configuration information includes: when the third container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for a current running container management controller corresponding to the third container management controller; the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in a computing node; the third container management controller sets container configuration information of a new container hosting controller corresponding to the currently-running container hosting controller according to the upgrade configuration information and the container configuration information of the currently-running container hosting controller, so that the new container hosting controller acquires a new version image according to the container configuration information, creates new containers corresponding to the currently-running containers managed by the currently-running container hosting controller according to the new version image, and deletes the currently-running containers corresponding to the new containers when detecting that the new containers normally run until the number of the currently-running containers managed by the currently-running container hosting controller corresponding to the third container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
Optionally, the currently-operated container is stopped first, and then a new container corresponding to the currently-operated container is operated. In the process, the active-standby switching occurs, and the active-standby switching is the most basic function of the database with high availability, so that the online service is not influenced, and the time is very short.
Thus, the number of the currently-operating containers managed by the currently-operating container hosting controller corresponding to the third container management controller is gradually reduced until the number of the currently-operating containers managed by each previously-operating container hosting controller corresponding to the third container management controller is 0. And simultaneously, the number of new version containers managed by the new container hosting controller is increased. But the third container management controller needs to ensure that the number of the current healthy containers cannot be smaller than the difference between the total number of the currently managed containers and the preset unavailable container threshold value. The preset unavailable container threshold is a maximum number of unavailable containers that the third container management controller may allow to exist.
Optionally, the creating, according to the new version image, a new container corresponding to each currently-running container managed by the currently-running container hosting controller includes: a target new container management controller acquires a current operation container managed by a current operation container management controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the computing node where the target current operation container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current operation container managed by the current operation container management controller as the target current operation container until the processing of all current operation containers managed by the current operation container management controller is completed.
Optionally, the YAML script is used to control the process of rolling and upgrading the containers in the computing nodes by the third container management controller according to the updated upgrade configuration information, and manual intervention is not required.
And 104, when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to the proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information.
Optionally, updating, according to the upgrade information, upgrade configuration information of a fourth container management controller corresponding to the proxy server in the distributed database includes: and setting the version identification and the storage address of the new version mirror image in the upgrading information as the version identification and the storage address of the new version mirror image in the upgrading configuration information of the fourth container management controller.
Optionally, the rolling upgrade of the container in the proxy server by the fourth container management controller according to the updated upgrade configuration information includes: when the fourth container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for a current running container management controller corresponding to the fourth container management controller; the system comprises a current operation container management controller, a proxy server and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the proxy server; the fourth container management controller sets the container configuration information of the new container hosting controller corresponding to the currently-running container hosting controller according to the upgrade configuration information and the container configuration information of the currently-running container hosting controller, so that the new container hosting controller acquires a new version image according to the container configuration information, creates new containers corresponding to the currently-running containers managed by the currently-running container hosting controller according to the new version image, and deletes the currently-running containers corresponding to the new containers when detecting that the new containers normally run until the number of the currently-running containers managed by the currently-running container hosting controller corresponding to the fourth container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
Optionally, the currently-operated container is stopped first, and then a new container corresponding to the currently-operated container is operated. In the process, the active-standby switching occurs, and the active-standby switching is the most basic function of the database with high availability, so that the online service is not influenced, and the time is very short.
Thus, the number of the currently-operating containers managed by the currently-operating container hosting controller corresponding to the fourth container management controller is gradually reduced until the number of the currently-operating containers managed by each previously-operating container hosting controller corresponding to the fourth container management controller is 0. And simultaneously, the number of new version containers managed by the new container hosting controller is increased. But the fourth container management controller needs to ensure that the number of the current healthy containers cannot be smaller than the difference between the total number of the currently managed containers and the preset unavailable container threshold value. The preset unavailable container threshold is a maximum number of unavailable containers that the fourth container management controller can allow to exist.
Optionally, the creating, according to the new version image, a new container corresponding to each currently-running container managed by the currently-running container hosting controller includes: a target new container management controller acquires a current operation container managed by a current operation container management controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the proxy server where the target current operation container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current operation container managed by the current operation container management controller as the target current operation container until the processing of all current operation containers managed by the current operation container management controller is completed.
Optionally, the YAML script is used to control the flow of rolling upgrade of the container in the proxy server by the fourth container management controller according to the updated upgrade configuration information, and no manual intervention is required.
Optionally, the method further includes: when any target node in the distributed database is detected to be failed to be upgraded, controlling the target node and an upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process;
the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server.
Optionally, the target node is a main storage node; the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes: and sending a rollback instruction to the first container management controller so that the first container management controller performs rollback on the containers in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
Optionally, the target node is a backup storage node; the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes: sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller; when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
Optionally, the target node is a computing node; the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes: sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the containers in the computing nodes according to the rollback instruction and the upgrade record information of the third container management controller; when detecting that the containers in the computing nodes finish rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller; when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
Optionally, the target node is a proxy server; the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes: sending a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on the container in the proxy server according to the rollback instruction and the upgrade record information of the fourth container management controller; when detecting that the container in the proxy server completes rollback, sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the container in the computing node according to the rollback instruction and the upgrade record information of the third container management controller; when detecting that the containers in the computing nodes finish rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller; when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
The embodiment of the invention provides a distributed database upgrading method, which is characterized in that a distributed database is deployed on the basis of a Kubernets container platform, and the main storage nodes, the backup storage nodes, the computing nodes and the proxy server in the distributed database are subjected to rolling upgrading according to a set sequence through container management controllers respectively corresponding to the main storage nodes, the backup storage nodes, the computing nodes and the proxy server, so that automatic rolling upgrading of all types of nodes in the distributed database is realized.
Example two
Fig. 2 is a flowchart of a distributed database upgrading method according to a second embodiment of the present invention. Embodiments of the invention may be combined with various alternatives in one or more of the embodiments described above.
As shown in fig. 2, the method of the embodiment of the present invention specifically includes:
step 201, updating the upgrade configuration information of the first container management controller corresponding to all the main storage nodes in the distributed database according to the upgrade information in the upgrade request, so that the first container management controller performs rolling upgrade on the containers in each main storage node according to the updated upgrade configuration information.
Wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
Step 202, when it is detected that the containers in the main storage nodes are upgraded, updating the upgrade configuration information of the second container management controller corresponding to all the backup storage nodes in the distributed database according to the upgrade information, so that the second container management controller performs rolling upgrade on the containers in the backup storage nodes according to the updated upgrade configuration information.
And 203, when it is detected that the containers in the backup storage nodes are upgraded, updating the upgrade configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrade information, so that the third container management controller performs rolling upgrade on the containers in the computing nodes according to the updated upgrade configuration information.
And 204, when the container in the computing node is detected to be upgraded, updating the upgrade configuration information of a fourth container management controller corresponding to the proxy server in the distributed database according to the upgrade information, so that the fourth container management controller performs rolling upgrade on the container in the proxy server according to the updated upgrade configuration information.
Step 205, when it is detected that the proxy server in the distributed database fails to be upgraded, sending a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on the container in the proxy server according to the rollback instruction and upgrade record information of the fourth container management controller.
Optionally, the rolling back the container in the proxy server by the fourth container management controller according to the rolling back instruction and the upgrade record information of the fourth container management controller includes: and when detecting a rollback instruction, the fourth container management controller controls the current running container hosting controller corresponding to the fourth container management controller before the upgrade according to the information related to the upgrade process recorded in the upgrade recording information of the fourth container management controller, creates a container before the upgrade corresponding to each new container according to the version image corresponding to the current running container hosting controller, and deletes the new container corresponding to each new container before the upgrade until the number of the new containers is 0 when detecting that each container before the upgrade normally runs. Thus, the upgraded new container is rolled back to the pre-upgrade version.
Step 206, when it is detected that the container in the proxy server completes rollback, sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the container in the compute node according to the rollback instruction and the upgrade record information of the third container management controller.
Optionally, the third container management controller performs rollback on the container in the proxy server according to the rollback instruction and the upgrade record information of the third container management controller, including: and when detecting a rollback instruction, the third container management controller controls the current running container hosting controller corresponding to the third container management controller before the upgrade according to the information related to the upgrade process recorded in the upgrade recording information of the third container management controller, creates a container before the upgrade corresponding to each new container according to the version image corresponding to the current running container, and deletes the new container corresponding to each new container before the upgrade until the number of the new containers is 0 when detecting that each container before the upgrade normally runs. Thus, the upgraded new container is rolled back to the pre-upgrade version.
Step 207, when detecting that the container in the computing node completes rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the container in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller.
Optionally, the rolling back the container in the proxy server by the second container management controller according to the rolling back instruction and the upgrade record information of the second container management controller includes: and when detecting a rollback instruction, the second container management controller controls the current running container management controller corresponding to the second container management controller before the upgrade according to the information related to the upgrade process recorded in the upgrade record information of the second container management controller, creates a container before the upgrade corresponding to each new container according to the version image corresponding to the current running container, and deletes the new container corresponding to each new container before the upgrade until the number of the new containers is 0 when detecting that each container before the upgrade normally runs. Thus, the upgraded new container is rolled back to the pre-upgrade version.
And 208, when it is detected that the containers in the backup storage nodes complete rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the containers in the main storage nodes according to the rollback instruction and the upgrade record information of the first container management controller.
Optionally, the rolling back the container in the proxy server by the first container management controller according to the rolling back instruction and the upgrade record information of the first container management controller includes: when the first container management controller detects a rollback instruction, the first container management controller controls the current running container management controller corresponding to the first container management controller before the upgrade according to the information related to the upgrade process recorded in the upgrade record information of the first container management controller, creates a container before the upgrade corresponding to each new container according to the version image corresponding to the current running container, and deletes the new container corresponding to each new container before the upgrade until the number of the new containers is 0 when the normal running of each container before the upgrade is detected. Thus, the upgraded new container is rolled back to the pre-upgrade version.
The embodiment of the invention provides a distributed database upgrading method, which controls a target node and an upgraded node in a distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process when the upgrading failure of a proxy server in the distributed database is detected, can realize automatic rollback when the upgrading failure of the proxy server in the distributed database is detected, can solve the problems of service interruption and rollback in the upgrading process, and really realizes lossless switching.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a distributed database upgrading apparatus according to a third embodiment of the present invention. The apparatus may be implemented in software and/or hardware and may generally be integrated in a computer device. As shown in fig. 3, the apparatus includes: primary storage node upgrade module 301, backup storage node upgrade module 302, compute node upgrade module 303, and proxy server upgrade module 304.
The main storage node upgrading module 301 is configured to update, according to the upgrading information in the upgrading request, upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database, so that the first container management controller performs rolling upgrading on containers in each main storage node according to the updated upgrading configuration information; the backup storage node upgrading module 302 is configured to, when it is detected that the containers in the main storage nodes are upgraded, update, according to the upgrade information, upgrade configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database, so that the second container management controller performs rolling upgrade on the containers in the backup storage nodes according to the updated upgrade configuration information; the computing node upgrading module 303 is configured to, when it is detected that the containers in the backup storage nodes are upgraded, update, according to the upgrade information, upgrade configuration information of a third container management controller corresponding to the computing nodes in the distributed database, so that the third container management controller performs rolling upgrade on the containers in the computing nodes according to the updated upgrade configuration information; the proxy server upgrading module 304 is configured to, when it is detected that the container in the computing node is upgraded, update, according to the upgrade information, upgrade configuration information of a fourth container management controller corresponding to the proxy server in the distributed database, so that the fourth container management controller performs rolling upgrade on the container in the proxy server according to the updated upgrade configuration information; wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
The embodiment of the invention provides a distributed database upgrading device, which deploys a distributed database based on a Kubernetes container platform, and performs rolling upgrading on a main storage node, a backup storage node, a computing node and an agent server in the distributed database according to a set sequence through container management controllers respectively corresponding to the main storage node, the backup storage node, the computing node and the agent server, so that automatic rolling upgrading of various types of nodes in the distributed database is realized.
On the basis of the foregoing embodiments, the distributed database upgrading apparatus may further include: the node rollback module is used for controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process when the upgrading failure of any target node in the distributed database is detected; the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server.
On the basis of the above embodiments, the target node is a main storage node; the node rollback module comprises: and the main node rollback unit is used for sending a rollback instruction to the first container management controller so that the first container management controller performs rollback on the containers in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
On the basis of the above embodiments, the target node is a proxy server; the node rollback module comprises: a first rollback unit, configured to send a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on a container in the proxy server according to the rollback instruction and upgrade record information of the fourth container management controller; a second rollback unit, configured to send a rollback instruction to the third container management controller when it is detected that the container in the proxy server completes rollback, so that the third container management controller performs rollback on the container in the compute node according to the rollback instruction and the upgrade record information of the third container management controller; a third rollback unit, configured to send a rollback instruction to the second container management controller when it is detected that the container in the computing node completes rollback, so that the second container management controller performs rollback on the container in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller; and the fourth rollback unit is configured to send a rollback instruction to the first container management controller when detecting that the container in each backup storage node completes rollback, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
On the basis of the foregoing embodiments, the performing, by the first container management controller, rolling upgrade on the container in each primary storage node according to the updated upgrade configuration information includes: when the first container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the first container management controller; the system comprises a current operation container management controller, a main storage node and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the main storage node; the first container management controller sets container configuration information of a new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the first container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
On the basis of the foregoing embodiments, each new container hosting controller creating, according to the container configuration information, a new container corresponding to each currently-operating container managed by the corresponding currently-operating container hosting controller includes: a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the main storage node where the target current running container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
The distributed database upgrading device can execute the distributed database upgrading method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects for executing the distributed database upgrading method.
Example four
Fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention. As shown in fig. 4, the computer apparatus includes a processor 410, a memory 420, an input device 430, and an output device 440; the number of the processors 410 in the computer device may be one or more, and one processor 410 is taken as an example in fig. 4; the processor 410, the memory 420, the input device 430 and the output device 440 in the computer apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 4.
Memory 420 serves as a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to a distributed database upgrade method in an embodiment of the present invention (e.g., primary storage node upgrade module 301, backup storage node upgrade module 302, compute node upgrade module 303, and proxy server upgrade module 304 in a distributed database upgrade apparatus). The processor 410 executes various functional applications and data processing of the computer device by executing software programs, instructions and modules stored in the memory 420, namely, implements one of the distributed database upgrading methods described above. That is, the program when executed by the processor implements: updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information; when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information; when the fact that the containers in the backup storage nodes are upgraded is detected, updating upgrading configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information; when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information; wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
The memory 420 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 420 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 420 may further include memory located remotely from processor 410, which may be connected to a computer device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 430 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer apparatus, and may include a keyboard and a mouse, etc. The output device 440 may include a display device such as a display screen.
On the basis of the above embodiments, the processor 410 further performs the following operations: when any target node in the distributed database is detected to be failed to be upgraded, controlling the target node and an upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process; the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server.
On the basis of the above embodiments, the target node is a main storage node; the processor 410 is configured to control the target node and the upgraded nodes in the distributed database to rollback according to a rollback order that is opposite to the node upgrade order during the upgrade process, by: and sending a rollback instruction to the first container management controller so that the first container management controller performs rollback on the containers in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
On the basis of the above embodiments, the target node is a proxy server; the processor 410 is configured to control the target node and the upgraded nodes in the distributed database to rollback according to a rollback order that is opposite to the node upgrade order during the upgrade process, by: sending a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on the container in the proxy server according to the rollback instruction and the upgrade record information of the fourth container management controller; when detecting that the container in the proxy server completes rollback, sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the container in the computing node according to the rollback instruction and the upgrade record information of the third container management controller; when detecting that the containers in the computing nodes finish rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller; when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
On the basis of the foregoing embodiments, the performing, by the first container management controller, rolling upgrade on the container in each primary storage node according to the updated upgrade configuration information includes: when the first container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the first container management controller; the system comprises a current operation container management controller, a main storage node and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the main storage node; the first container management controller sets container configuration information of a new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the first container management controller is 0; and the new container is a new version container corresponding to the new version mirror image.
On the basis of the foregoing embodiments, each new container hosting controller creating, according to the container configuration information, a new container corresponding to each currently-operating container managed by the corresponding currently-operating container hosting controller includes: a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container; the target new container hosting controller creates a new container corresponding to the new version mirror image in the main storage node where the target current running container is located; the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container; the target new container hosting controller operates the new container corresponding to the target current operation container; and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
EXAMPLE five
Fifth, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the distributed database upgrading method provided in any embodiment of the present invention. Of course, the embodiment of the present invention provides a computer-readable storage medium, which can perform related operations in a distributed database upgrading method provided by any embodiment of the present invention. That is, the computer program when executed by the processor implements: updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information; when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information; when the fact that the containers in the backup storage nodes are upgraded is detected, updating upgrading configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information; when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information; wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the distributed database upgrading apparatus, the included units and modules are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be understood that the foregoing is only illustrative of the presently preferred embodiments of the invention and that various modifications and changes in the techniques employed are possible. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (13)

1. A distributed database upgrade method, comprising:
updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information;
when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information;
when the fact that the containers in the backup storage nodes are upgraded is detected, updating upgrading configuration information of a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information;
when the fact that the container in the computing node is upgraded is detected, updating upgrading configuration information of a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information;
wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
2. The method of claim 1, further comprising:
when any target node in the distributed database is detected to be failed to be upgraded, controlling the target node and an upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process;
the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server.
3. The method of claim 2, wherein the target node is a master storage node;
the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes:
and sending a rollback instruction to the first container management controller so that the first container management controller performs rollback on the containers in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
4. The method of claim 2, wherein the target node is a proxy server;
the step of controlling the target node and the upgraded node in the distributed database to rollback according to a rollback sequence opposite to the node upgrading sequence in the upgrading process includes:
sending a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on the container in the proxy server according to the rollback instruction and the upgrade record information of the fourth container management controller;
when detecting that the container in the proxy server completes rollback, sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the container in the computing node according to the rollback instruction and the upgrade record information of the third container management controller;
when detecting that the containers in the computing nodes finish rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller;
when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
5. The method of claim 1, wherein the first container management controller performs rolling upgrade on the containers in the respective primary storage nodes according to the updated upgrade configuration information, and comprises:
when the first container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the first container management controller;
the system comprises a current operation container management controller, a main storage node and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the main storage node;
the first container management controller sets container configuration information of a new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the first container management controller is 0;
and the new container is a new version container corresponding to the new version mirror image.
6. The method of claim 5, wherein creating a new container from the new version image corresponding to each currently running container managed by the corresponding currently running container hosting controller comprises:
a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container;
the target new container hosting controller creates a new container corresponding to the new version mirror image in the main storage node where the target current running container is located;
the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container;
the target new container hosting controller operates the new container corresponding to the target current operation container;
and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
7. A computer device comprising a processor and a memory, the memory to store instructions that, when executed, cause the processor to:
updating the upgrading configuration information of a first container management controller corresponding to all main storage nodes in the distributed database according to the upgrading information in the upgrading request, so that the first container management controller performs rolling upgrading on containers in all the main storage nodes according to the updated upgrading configuration information;
when the containers in the main storage nodes are detected to be upgraded, updating upgrading configuration information of a second container management controller corresponding to all backup storage nodes in the distributed database according to the upgrading information so that the second container management controller can perform rolling upgrading on the containers in the backup storage nodes according to the updated upgrading configuration information;
when the fact that the containers in the backup storage nodes are upgraded is detected, updating a third container management controller corresponding to the computing nodes in the distributed database according to the upgrading information, so that the third container management controller can carry out rolling upgrading on the containers in the computing nodes according to the updated upgrading configuration information;
when the fact that the container in the computing node is upgraded is detected, updating a fourth container management controller corresponding to a proxy server in the distributed database according to the upgrading information, so that the fourth container management controller can carry out rolling upgrading on the container in the proxy server according to the updated upgrading configuration information;
wherein the distributed database is deployed based on a Kubernets container platform, comprising: the system comprises at least one main storage node, first container management controllers corresponding to all the main storage nodes, at least one backup storage node corresponding to each main storage node, second container management controllers corresponding to all the backup storage nodes, a computing node, a third container management controller corresponding to the computing node, a proxy server and a fourth container management controller corresponding to the proxy server.
8. The computer device of claim 7, wherein the processor further performs the following operations:
when any target node in the distributed database is detected to be failed to be upgraded, controlling the target node and an upgraded node in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process;
the target node may be a primary storage node, a backup storage node, a computing node, or a proxy server.
9. The computer device of claim 8, wherein the target node is a master storage node; the processor is configured to control the target node and the upgraded nodes in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process by the following method:
and sending a rollback instruction to the first container management controller so that the first container management controller performs rollback on the containers in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
10. The computer device of claim 8, wherein the target node is a proxy server; the processor is configured to control the target node and the upgraded nodes in the distributed database to rollback according to a rollback sequence opposite to a node upgrading sequence in an upgrading process by the following method:
sending a rollback instruction to the fourth container management controller, so that the fourth container management controller performs rollback on the container in the proxy server according to the rollback instruction and the upgrade record information of the fourth container management controller;
when detecting that the container in the proxy server completes rollback, sending a rollback instruction to the third container management controller, so that the third container management controller performs rollback on the container in the computing node according to the rollback instruction and the upgrade record information of the third container management controller;
when detecting that the containers in the computing nodes finish rollback, sending a rollback instruction to the second container management controller, so that the second container management controller performs rollback on the containers in each backup storage node according to the rollback instruction and the upgrade record information of the second container management controller;
when detecting that the container in each backup storage node finishes rollback, sending a rollback instruction to the first container management controller, so that the first container management controller performs rollback on the container in each main storage node according to the rollback instruction and the upgrade record information of the first container management controller.
11. The computer device of claim 7, wherein the first container management controller performs rolling upgrade on the containers in the respective master storage nodes according to the updated upgrade configuration information, and comprises:
when the first container management controller detects that the upgrade configuration information is updated, a corresponding new container management controller is established for each current operation container management controller corresponding to the first container management controller;
the system comprises a current operation container management controller, a main storage node and a plurality of current operation containers, wherein the current operation container management controller is used for managing at least one current operation container, and each current operation container is a container in the main storage node;
the first container management controller sets container configuration information of a new container hosting controller corresponding to each currently-running container hosting controller according to the upgrade configuration information and the container configuration information of each currently-running container hosting controller, so that each new container hosting controller acquires a new version image according to the container configuration information, creates a new container corresponding to each currently-running container managed by the corresponding currently-running container hosting controller according to the new version image, and deletes the currently-running container corresponding to each new container when detecting that each new container runs normally until the number of currently-running containers managed by each currently-running container hosting controller corresponding to the first container management controller is 0;
and the new container is a new version container corresponding to the new version mirror image.
12. The computer device of claim 11, wherein each new container hosting controller creates a new container corresponding to each currently running container managed by the corresponding currently running container hosting controller according to the container configuration information, comprising:
a target new container pipe supporting controller acquires a current operation container managed by a corresponding current operation container pipe supporting controller as a target current operation container;
the target new container hosting controller creates a new container corresponding to the new version mirror image in the main storage node where the target current running container is located;
the target new container hosting controller acquires the configuration information of the target current operation container from the target current operation container, writes the configuration information of the target current operation container into the new container, and determines the new container as a new container corresponding to the target current operation container;
the target new container hosting controller operates the new container corresponding to the target current operation container;
and the target new container management controller returns to execute the operation of acquiring one current running container managed by the corresponding current running container management controller as the target current running container until the processing of all current running containers managed by the corresponding current running container management controller is finished.
13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the distributed database upgrading method as claimed in any one of claims 1 to 6.
CN202011295446.3A 2020-11-18 2020-11-18 Distributed database upgrading method, device and medium Pending CN112434008A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011295446.3A CN112434008A (en) 2020-11-18 2020-11-18 Distributed database upgrading method, device and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011295446.3A CN112434008A (en) 2020-11-18 2020-11-18 Distributed database upgrading method, device and medium

Publications (1)

Publication Number Publication Date
CN112434008A true CN112434008A (en) 2021-03-02

Family

ID=74694140

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011295446.3A Pending CN112434008A (en) 2020-11-18 2020-11-18 Distributed database upgrading method, device and medium

Country Status (1)

Country Link
CN (1) CN112434008A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113448609A (en) * 2021-08-30 2021-09-28 恒生电子股份有限公司 Container upgrading method, device, equipment and storage medium
CN113572831A (en) * 2021-07-21 2021-10-29 重庆星环人工智能科技研究院有限公司 Communication method between Kubernetes clusters, computer equipment and medium
CN113704026A (en) * 2021-10-28 2021-11-26 北京时代正邦科技股份有限公司 Distributed financial memory database security synchronization method, device and medium
CN115827789A (en) * 2023-02-21 2023-03-21 苏州浪潮智能科技有限公司 Method, system, equipment and storage medium for optimizing file type database upgrading

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030233648A1 (en) * 2002-06-12 2003-12-18 Earl William J. System and method for managing software upgrades in a distributed computing system
CN107515776A (en) * 2017-07-18 2017-12-26 深信服科技股份有限公司 The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing
CN108052336A (en) * 2017-12-08 2018-05-18 国云科技股份有限公司 A kind of distributed software upgrade-system and its implementation
CN111614490A (en) * 2020-04-29 2020-09-01 北京金山云网络技术有限公司 Management system and method for managed container cluster based on top-level container cluster
CN111752581A (en) * 2020-05-22 2020-10-09 中国邮政储蓄银行股份有限公司 Distributed system upgrading method and device and computer system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030233648A1 (en) * 2002-06-12 2003-12-18 Earl William J. System and method for managing software upgrades in a distributed computing system
CN107515776A (en) * 2017-07-18 2017-12-26 深信服科技股份有限公司 The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing
CN108052336A (en) * 2017-12-08 2018-05-18 国云科技股份有限公司 A kind of distributed software upgrade-system and its implementation
CN111614490A (en) * 2020-04-29 2020-09-01 北京金山云网络技术有限公司 Management system and method for managed container cluster based on top-level container cluster
CN111752581A (en) * 2020-05-22 2020-10-09 中国邮政储蓄银行股份有限公司 Distributed system upgrading method and device and computer system

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113572831A (en) * 2021-07-21 2021-10-29 重庆星环人工智能科技研究院有限公司 Communication method between Kubernetes clusters, computer equipment and medium
CN113572831B (en) * 2021-07-21 2024-03-15 重庆星环人工智能科技研究院有限公司 Communication method, computer equipment and medium between Kubernetes clusters
CN113448609A (en) * 2021-08-30 2021-09-28 恒生电子股份有限公司 Container upgrading method, device, equipment and storage medium
CN113704026A (en) * 2021-10-28 2021-11-26 北京时代正邦科技股份有限公司 Distributed financial memory database security synchronization method, device and medium
CN115827789A (en) * 2023-02-21 2023-03-21 苏州浪潮智能科技有限公司 Method, system, equipment and storage medium for optimizing file type database upgrading

Similar Documents

Publication Publication Date Title
CN107515776B (en) Method for upgrading service continuously, node to be upgraded and readable storage medium
CN112434008A (en) Distributed database upgrading method, device and medium
US9960963B2 (en) Dynamic client fail-over during a rolling patch installation based on temporal server conditions
US10635473B2 (en) Setting support program, setting support method, and setting support device
EP4083786A1 (en) Cloud operating system management method and apparatus, server, management system, and medium
US20060259594A1 (en) Progressive deployment and maintenance of applications on a set of peer nodes
US10310900B2 (en) Operating programs on a computer cluster
CN111897558A (en) Kubernets upgrading method and device for container cluster management system
CN112753017A (en) Automation of management of cloud upgrades
CN108319492B (en) Method, device and system for resetting physical machine
CN112083889A (en) Data migration method, device, equipment and readable storage medium
CN112486466B (en) Method for realizing quick universal basic framework based on micro-service architecture
CN112199356B (en) Fault processing method, device, server and storage medium
US20210089379A1 (en) Computer system
US11757697B2 (en) System and method of distributed edge configuration management
US8689048B1 (en) Non-logging resumable distributed cluster
US11086615B2 (en) Virtual appliance upgrades in high-availability (HA) computing clusters
CN109189444A (en) A kind of upgrade control method and device of the management node of server virtualization system
CN115292408A (en) Master-slave synchronization method, device, equipment and medium for MySQL database
US11461131B2 (en) Hosting virtual machines on a secondary storage system
CN114610545A (en) Method, system, device and medium for reducing single point of failure of private cloud computing
WO2023198276A1 (en) Handling failure of an application instance
CN115878269A (en) Cluster migration method, related device and storage medium
CN116860279A (en) Workload execution on backend systems
CN116225617A (en) Management migration method and device for container instance, electronic equipment and storage medium

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20210302