A database cluster management method, device, equipment and storage medium
By establishing description files and bootstrap components to automate the management of database clusters, the problems of low efficiency and high error rate of manual management are solved, and efficient database cluster management is achieved.
Patent Information
- Application Number
- CN202211674677.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-26
- Publication Date
- 2026-02-13
- Estimated Expiration
- 2042-12-26
AI Technical Summary
In existing technologies, manual management of database clusters requires advanced operational and maintenance skills, is inefficient, and is prone to errors, which can affect the normal operation of the database.
By obtaining database cluster management requirements, creating description files, producing container images and adding bootloader components, determining the cluster master and slave databases, performing data synchronization and architecture management, and using bootloader components and description files to achieve automated management.
It has enabled automated management of database clusters, improved management efficiency, saved human resources, and avoided errors in manual management.
Smart Images

Figure CN116244269B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of database cluster management, and particularly relates to a database cluster management method and device, equipment and a storage medium. BACKGROUND
[0002] With the development of cloud computing technology, due to the demand for elasticity, high availability, scalability and the increasing demand for on-demand use from application programs in different business fields, cloud-native databases have become increasingly important. When enterprises face exponentially increasing mass storage demands, businesses also face more challenges from hot spots and burst traffic.
[0003] In the prior art, the database cluster is usually managed by manual operation, and the database backup file is made by manual operation, and the backup file is transmitted to the backup mirror for restoration, and the database cluster is expanded, contracted and maintained.
[0004] However, when the database cluster is managed by manual operation, the operation and maintenance technical requirements of the management personnel are high, and manual operation and maintenance is prone to slow efficiency and errors. When the database cluster is managed manually, the normal operation of the database is affected. SUMMARY
[0005] Therefore, it is necessary to provide a database cluster management method, device, equipment and storage medium to solve the problem that the operation and maintenance technical requirements of the management personnel are high when the database cluster is managed manually.
[0006] To achieve the above technical purpose, the present application adopts the following technical scheme:
[0007] In a first aspect, the present application provides a database cluster management method, comprising:
[0008] Obtaining database cluster management requirements, and establishing a description file according to the database cluster management requirements;
[0009] Making a container image of the database to be managed to obtain an image database, and adding a boot component to the image database;
[0010] Determining the cluster master and the cluster backup in the image database according to the boot component, and synchronizing the cluster data;
[0011] Managing the database architecture of the image database after data synchronization according to the description file.
[0012] Preferably, determining the cluster master and the cluster backup in the image database according to the boot component, and synchronizing the cluster data, comprises:
[0013] The guiding component sorts database containers of the image database, and determines the cluster master and the cluster standby in the image database according to the sorting result of the database containers.
[0014] The cluster master is backed up, and the cluster standby is synchronized according to the data backup of the cluster master.
[0015] Preferably, the description file includes the number of copies; the guiding component sorts database containers of the image database, and determines the cluster master and the cluster standby in the image database according to the sorting result of the database containers, including:
[0016] The guiding component sorts database containers of the image database according to the number of copies;
[0017] The database cluster corresponding to the first database container sorting is set as the cluster master, and the remaining database clusters are set as the cluster standby.
[0018] Preferably, the cluster master is backed up, and the cluster standby is synchronized according to the data backup of the cluster master, including:
[0019] The guiding component backs up the cluster master, and modifies the external interface state of the cluster master to allow external access;
[0020] The cluster standby polls the external interface of the cluster master;
[0021] When the external interface state of the cluster master is allowed to access externally, the cluster standby downloads the data backup of the cluster master, and modifies the external interface state of the cluster standby to allow external access, until the external interface state of all cluster standbys is allowed to access externally.
[0022] Preferably, the image database after data synchronization is managed according to the description file, including:
[0023] The image database after data synchronization is resource configured according to the description file;
[0024] The guiding component determines the architecture change of the image database, and sets the external interface of the image database to not allow external access;
[0025] The image database is managed according to the architecture change.
[0026] Preferably, the image database is managed according to the architecture change, including:
[0027] When the architecture change is to add a container node, the data backup of the cluster master is downloaded, the added container node is set as the cluster standby, and the external interface is set to allow external access.
[0028] 0 Preferably, the mirror database is managed according to the architecture change, including:
[0029] When the architecture change is that the container node needs to be deleted, the resource configuration interface is called, the corresponding container node is deleted according to the description file, and the container node information corresponding to the boot component is deleted.
[0030] In a second aspect, the present application further provides a database cluster management device, comprising:
[0031] The establishing module is configured to obtain a database cluster management requirement, and establish a description file according to the database cluster management requirement;
[0032] The adding module is configured to make a container image of a database to be managed to obtain a mirror database, and add a boot component to the mirror database;
[0033] The synchronizing module is configured to determine a cluster master and a cluster backup in the mirror database according to the boot component, and perform cluster data synchronization;
[0034] The management module is configured to manage a database architecture of the mirror database after data synchronization according to the description file.
[0035] In a third aspect, the present application further provides an electronic device, comprising a memory and a processor, wherein,
[0036] The memory is configured to store a program;
[0037] The processor is coupled with the memory and is configured to execute the program stored in the memory to implement the steps in the database cluster management method in any of the above implementation manners.
[0038] In a fourth aspect, the present application further provides a computer readable storage medium for storing computer readable programs or instructions, which, when executed by a processor, can implement the steps in the database cluster management method in any of the above implementation manners.
[0039] The beneficial effect of the above embodiment is that the application relates to a database cluster management method, device, equipment and storage medium, the method comprising: obtaining database cluster management requirements, establishing a description file according to the database cluster management requirements; making a container image of a database to be managed to obtain an image database, and adding a boot component to the image database; determining a cluster master library and a cluster backup library in the image database according to the boot component, and performing cluster data synchronization; and performing database architecture management on the image database after data synchronization according to the description file. The database cluster management method, device, equipment and storage medium provided by the application can establish a description file according to database cluster management requirements, realize automatic management of the database cluster through the description file, do not need manual management, have high management efficiency, and save human resources. BRIEF DESCRIPTION OF DRAWINGS
[0040] Figure 1 A flowchart of an embodiment of the database cluster management method provided by the application;
[0041] Figure 2 A flowchart of an embodiment of the data synchronization provided by the application;
[0042] Figure 3 A flowchart of an embodiment of the database architecture management provided by the application;
[0043] Figure 4 A structural diagram of an embodiment of the database cluster management device provided by the application;
[0044] Figure 5 A structural diagram of an electronic device provided by the embodiment of the application. DETAILED DESCRIPTION
[0045] The preferred embodiments of the application will be described in detail below with reference to the accompanying drawings, which form a part of this application. The accompanying drawings illustrate the principles of the application and, together with the description, serve to explain the application, but are not intended to limit the scope of the application.
[0046] In the description of the present application, the meaning of "a plurality of" is two or more than two, unless otherwise explicitly specified.
[0047] Before the embodiments of the application are described, the related terms are described as follows:
[0048] The Docker image can be regarded as a special file system, which contains not only programs, libraries, resources, configurations and other files required for container runtime, but also some configuration parameters prepared for runtime;
[0049] YAML is a human-readable, easy-to-understand format for expressing data serialization.
[0050] Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase that the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive of one another. As will be apparent to those of ordinary skill in the art, embodiments described herein can be combinable with other embodiments.
[0051] The application provides a database cluster management method, device and equipment and storage medium, which are described below.
[0052] Please refer to Figure 1 , Figure 1 The flowchart of an embodiment of the database cluster management method provided by the application, a specific embodiment of the application discloses a database cluster management method, which comprises the following steps:
[0053] S101, obtain a database cluster management requirement, and establish a description file according to the database cluster management requirement;
[0054] S102, make a container image of a database to be managed to obtain an image database, and add a boot component to the image database;
[0055] S103, determine a cluster master and a cluster standby in the image database according to the boot component, and perform cluster data synchronization;
[0056] S104, perform database architecture management on the image database after data synchronization according to the description file.
[0057] In the above embodiment, when a cloud-native database needs to be created on a container cloud platform, a description file in the yaml format needs to be created first. After obtaining a database cluster management requirement, a description file in the yaml format is established according to the database cluster management requirement. The content of the description file in the yaml format includes information such as an image version, a CPU, a memory, a storage size, a cluster type, and a number of replicas.
[0058] The database to be managed is a database to be managed according to the database cluster management requirement. The database to be managed is made into a docker container image, and a database cluster boot component is implanted in the database image. The component mainly realizes the allocation of roles of the database cluster nodes under different architectures.
[0059] According to the number of replicas described in the yaml file, the database container is sorted, the guiding component sets the first database as the master library, and the other databases as the backup library, and according to the configuration file specified by the core controller, the cluster is guided, and the database sub-node member is precisely idempotent configuration.
[0060] The database architecture management includes, but is not limited to, database cluster type change, database cluster expansion and contraction, etc., and has corresponding database architecture management settings in the description file. The mirror database after data synchronization is subjected to corresponding database architecture management through the description file.
[0061] Compared with the prior art, the database cluster management method, device, equipment and storage medium provided by the embodiment, the method comprises: obtaining a database cluster management requirement, establishing a description file according to the database cluster management requirement; making a container image of a database to be managed to obtain a mirror database, and adding a guiding component to the mirror database; determining the cluster master library and the cluster backup library in the mirror database according to the guiding component, and performing cluster data synchronization; and performing database architecture management on the mirror database after data synchronization according to the description file. The database cluster management method, device, equipment and storage medium provided by the present application can establish a description file according to the database cluster management requirement, and realize automatic management of the database cluster through the description file, without manual management, high management efficiency, and saving of human resources.
[0062] In some embodiments of the present application, determining the cluster master library and the cluster backup library in the mirror database according to the guiding component and performing cluster data synchronization comprises:
[0063] The guiding component sorts the database containers of the mirror database, and determines the cluster master library and the cluster backup library in the mirror database according to the database container sorting result.
[0064] The data of the cluster master library is backed up, and the data of the cluster backup library is synchronized according to the data backup of the cluster master library.
[0065] In the above embodiment, the guiding component can guide the mirror database, obtain the capacity status of the database containers of each cluster node in the mirror database, and sort according to the capacity status of the database containers. According to the database container sorting result, the cluster master library and the cluster backup library in the mirror database are determined according to the set sorting rule.
[0066] The data content in the cluster master library is more important, and can manage the database, so the data content in the cluster master library needs to be backed up, and the data of the cluster backup library is synchronized according to the data backup of the cluster master library.
[0067] In some embodiments of the present application, the description file includes the number of copies; the database container of the image database is sorted by the boot component, and the cluster master and the cluster backup in the image database are determined according to the sorting result of the database container, including:
[0068] Based on the boot component, the database container of the image database is sorted according to the number of copies;
[0069] The database cluster corresponding to the first database container sorting is set as the cluster master, and the remaining database clusters are set as the cluster backup.
[0070] In the above embodiment, the number of copies of the image database container description can be obtained according to the yaml description file, the image database container is sorted by the boot component, the sorting result of the image database container is obtained, the cluster master and the cluster backup are divided according to the sorting result, and the database cluster corresponding to the first database container sorting is set as the cluster master, and the remaining database clusters are set as the cluster backup.
[0071] When the self is the master, the backup file of the self is made, and the backup download service is published externally. When the backup library is started and the self is not the master through the boot file, the backup download service in the cluster is waited to be ready, the backup download service is checked to be ready, the backup file is downloaded actively, and the database of the self is restored. After the restoration, the boot component executes the sql statement to mark the database role of the self, and waits for the cluster data synchronization.
[0072] Please refer to Figure 2 , Figure 2 The flowchart of an embodiment of the data synchronization provided by the present application is shown. In some embodiments of the present application, the cluster master is backed up, and the cluster backup is synchronized according to the data backup of the cluster master, including:
[0073] S201, the data of the cluster master is backed up by the boot component, and the state of the external interface of the cluster master is modified to allow external access;
[0074] S202, the cluster backup polls the external interface of the cluster master;
[0075] S203, when the state of the external interface of the cluster master is allowed to access externally, the cluster backup downloads the data backup of the cluster master, and modifies the state of the external interface of the cluster backup to allow external access, until the state of the external interface of all cluster backups is allowed to access externally.
[0076] In the above embodiment, the boot file starts the database in the image ranked first in the single machine mode, makes a database backup file for booting other databases in the cluster, modifies the database configuration file after the operation is completed, and starts the current database in the cluster mode, modifies the current database mode to the master database, and marks the external interface as ready, that is, sets the external interface state of the cluster master database to allow external access.
[0077] Then the other database boot component polls the external interface of the cluster master database, and when it finds that the external interface state of the cluster master database is ready, the boot component downloads the backup file in the cluster master database and restores other databases in the images ranked after the first one, modifies the mode of the other databases to the cluster standby database, and marks the data external interface of the cluster standby database as ready after the operation is completed, that is, sets the external interface state of the cluster standby database to allow external access.
[0078] Please refer to Figure 3 , Figure 3 The flowchart of an embodiment of the database architecture management provided by the application is shown in the figure. In some embodiments of the application, the database architecture management is performed on the image database after data synchronization according to the description file, which includes the following steps.
[0079] S301, resource configuration is performed on the image database after data synchronization according to the description file.
[0080] S302, the boot component determines the architecture change of the image database, and sets the external interface of the image database to not allow external access.
[0081] S303, the image database is managed according to the architecture change.
[0082] In the above embodiment, after the resource controller receives the yaml description file, the information of the description file is converted into statefulset, configmap, secret, service, PersistentVolumeClaim and other resource configurations in the kubenetes cluster, and the corresponding resources are created by calling the kubernetes api interface. After the kubernetes cluster receives the information, the corresponding resources are created on the corresponding nodes and clusters through the scheduler, and the cloud native database container is run through the kubelet agent tool of kubernetes.
[0083] It should be noted that the resource controller is used to accurately manage the database custom resource by using the kubernetes coordinator technology, the resource controller can accept a configuration file in yaml format, the configuration file describes the image version, cpu, memory, storage size, cluster type, number of replicas and other information used by the database, the resource controller converts the information into statefulset, configmap, secret, service, PersistentVolumeClaim and other resource configurations that can be recognized by the kubernetes cluster, realizes the scheduling and deployment of the database based on the kubernetes cluster, so that the kubernetes can accurately run the database configuration described in the yaml file, and achieves the purpose of running the database in the kubernetes cluster. Among them, the statefulset resource control node pod starts in sequence, realizes pod rolling change and rotation downtime, and the main program running in the pod is the database, the configmap resource is used to manage the configuration file required by the database cluster, the secret resource is used to manage the database encryption and authentication information storage file, the service resource is used to manage the database service traffic forwarding control configuration file, control the service access between cluster nodes and the service access of the cluster to the outside, and the PersistentVolumeClaim resource is used to manage the persistent storage volume claim user storage database file. After the kubernetes api accepts the above resources, the scheduler in the kubernetes calculates the node resources, and notifies the kubelet on the cluster worker node that meets the running condition to start the database container, so that the database can correctly run in the kubernetes cluster.
[0084] The architecture change of the image database is determined through the guidance component, and the external interface of the image database is set to not allow external access to avoid misoperation and cause data loss or error in the database cluster.
[0085] In some embodiments of the application, the image database is managed according to the architecture change, including:
[0086] When the architecture change is to add a container node, the data backup of the cluster master library is downloaded, the added container node is set as a cluster standby library, and the external interface is set to allow external access.
[0087] In the above embodiment, when the cluster needs to be changed, the resource controller receives a new yaml description file, converts the information into statefulset, configmap, secret, service, PersistentVolumeClaim and other resource configurations in the kubenetes cluster, compares the information before and after the database, and then modifies the information that has changed. When the boot component in the cloud native database container finds that the cluster needs to be changed, the external interface is marked as unready, and the cluster architecture before and after modification is compared.
[0088] If a new container node is needed, a backup file needs to be made in the first database container. After the backup file is made, the interface is marked as ready. After checking the interface in the new container node, the backup file is downloaded, the boot component guides the new node database to start, and the database mode of the boot component is modified to a backup database, and then the corresponding interface is modified to ready.
[0089] In some embodiments of the present application, the image database is managed according to the architecture change, including:
[0090] When the architecture change is to delete a container node, the resource configuration interface is called, the corresponding container node is deleted according to the description file, and the container node information of the boot component is deleted.
[0091] In the above embodiment, when the cluster needs to delete a node, the resource controller calls the kubernate api interface to delete the corresponding database container, the boot component in the cloud native database container receives the change information, finds that the change operation is to delete a replica, modifies the corresponding configuration file, deletes the database information to be deleted from the configuration file, and then restarts the database to take effect.
[0092] When the architecture change is to delete a container node, the resource configuration interface is called, the corresponding container node is deleted according to the description file, and the container node information of the boot component is deleted.
[0093] In order to better implement the database cluster management method in the embodiment of the present application, on the basis of the database cluster management method, please refer to Figure 4 , Figure 4 The structure diagram of an embodiment of the database cluster management device provided by the present application, the embodiment of the present application provides a database cluster management device 400, which comprises: a establishing module 410, used for obtaining database cluster management requirements, and establishing a description file according to the database cluster management requirements;
[0094] An adding module 420 is used for making a container image of a database to be managed to obtain an image database, and adding a boot component to the image database;
[0095] The synchronization module 430 is configured to determine the cluster master and the cluster standby in the mirror database according to the guide component, and perform cluster data synchronization.
[0096] The management module 440 is configured to perform database architecture management on the mirror database after data synchronization according to the description file.
[0097] It should be noted that the apparatus 400 provided in the above embodiments can implement the technical solutions described in the above method embodiments, and the principles of the implementation of the above modules or units can be referred to the corresponding content in the above method embodiments, which will not be described here.
[0098] Please refer to Figure 5 , Figure 5 The structure schematic diagram of the electronic device provided in the embodiments of the present application. Based on the above database cluster management method, the present application also correspondingly provides a database cluster management device. The database cluster management device can be a mobile terminal, a desktop computer, a notebook computer, a palm computer, a server and other computing devices. The database cluster management device comprises a processor 510, a memory 520 and a display 530.
[0099] Only part of the components of the electronic device are shown, but it should be understood that all the shown components are not required, and more or less components can be alternatively implemented. Figure 5
[0100] The memory 520 can be an internal storage unit of the database cluster management device in some embodiments, for example, a hard disk or a memory of the database cluster management device. The memory 520 can also be an external storage device of the database cluster management device in other embodiments, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card and the like equipped on the database cluster management device. Further, the memory 520 can include both the internal storage unit and the external storage device of the database cluster management device. The memory 520 is used to store application software installed on the database cluster management device and various data, for example, program codes installed on the database cluster management device and the like. The memory 520 can also be used to temporarily store data that has been output or will be output. In an embodiment, the memory 520 stores a database cluster management program 540, which can be executed by the processor 510, so as to implement the database cluster management method of the embodiments of the present application.
[0101] The processor 510 may, in some embodiments, be a central processing unit (CPU), microprocessor, or other data processing chip for running program codes or processing data stored in the memory 520, such as performing the management method of the database cluster.
[0102] The display 530 may, in some embodiments, be an LED display, liquid crystal display, touch liquid crystal display, OLED (Organic Light-Emitting Diode) touch, or the like. The display 530 is used to display information of the database cluster management device and to display a visualized user interface. The components 510-530 of the database cluster management device communicate with each other through a system bus.
[0103] In an embodiment, the steps in the above database cluster management method are implemented when the processor 510 executes the database cluster management program 540 in the memory 520.
[0104] The embodiment also provides a computer-readable storage medium having a database cluster management program stored thereon, which, when executed by a processor, implements the following steps:
[0105] Obtaining a database cluster management requirement, and establishing a description file according to the database cluster management requirement;
[0106] Making a container image of a database to be managed to obtain an image database, and adding a boot component to the image database;
[0107] Determining a cluster master and a cluster standby in the image database according to the boot component, and performing cluster data synchronization;
[0108] Performing database architecture management on the image database after data synchronization according to the description file.
[0109] In summary, the embodiment provides a database cluster management method, device, equipment, and storage medium, which includes: obtaining a database cluster management requirement, and establishing a description file according to the database cluster management requirement; making a container image of a database to be managed to obtain an image database, and adding a boot component to the image database; determining a cluster master and a cluster standby in the image database according to the boot component, and performing cluster data synchronization; and performing database architecture management on the image database after data synchronization according to the description file. The database cluster management method, device, equipment, and storage medium provided by the embodiment can establish a description file according to a database cluster management requirement, and realize automatic management of a database cluster through the description file, without manual management, which is efficient and saves human resources.
[0110] The above description is only the preferred embodiment of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application.
Claims
1. A method for managing a database cluster, characterized in that, include: Obtain the database cluster management requirements, and create a description file based on the database cluster management requirements; Create a container image of the database to be managed to obtain an image database, and add a bootstrap component to the image database. The bootstrap component is used to assign roles to the cluster nodes of the database to be managed under different architectures. The process of determining the cluster master database and cluster standby database in the image database based on the bootstrapping component and synchronizing cluster data includes: sorting the database containers of the image database using the bootstrapping component; determining the cluster master database and cluster standby database in the image database based on the database container sorting results; backing up the data of the cluster master database; and synchronizing the data of the cluster standby database based on the data backup of the cluster master database. The database architecture management is performed on the mirrored database after data synchronization according to the description file; The description file includes the number of replicas; the step of sorting the database containers of the image database through the bootstrap component, and determining the cluster master and cluster standby databases in the image database based on the database container sorting result, includes: Based on the bootstrap component, the mirror database is sorted into database containers according to the number of replicas; Set the database cluster corresponding to the first database container in the sort order as the cluster master database, and set the remaining database clusters as cluster slave databases. The step of backing up the data in the cluster master database and synchronizing the data in the cluster standby database based on the data backup of the cluster master database includes: The bootstrapping component performs data backup on the cluster master database and modifies the external interface status of the cluster master database to allow external access. The cluster backup database polls the external interface of the cluster master database. When the external interface status of the cluster master database is allowed to access the outside world, the cluster backup database downloads the data backup of the cluster master database and modifies the external interface status of the cluster backup database to be allowed to access the outside world, until the external interface status of all the cluster backup databases is allowed to access the outside world.
2. The database cluster management method according to claim 1, characterized in that, The step of managing the database architecture of the mirrored database after data synchronization according to the description file includes: Configure resources for the mirror database after data synchronization according to the description file; The bootstrapping component determines the architectural changes of the mirror database and sets the external interface of the mirror database to be disabled. The mirror database is managed according to the changes in the architecture.
3. The database cluster management method according to claim 2, characterized in that, The management of the mirror database based on the changes in the architecture includes: When the architecture changes to the point that a new container node needs to be added, the data backup of the cluster master database is downloaded, and the newly added container node is set as the cluster backup database, with its external interface set to allow external access.
4. The database cluster management method according to claim 2, characterized in that, The management of the mirror database based on the changes in the architecture includes: When the architecture changes to the point where container nodes need to be deleted, the resource configuration interface is called to delete the corresponding container nodes according to the description file, and the container node information corresponding to the bootstrap component is also deleted.
5. A database cluster management device, characterized in that, include: A module is established to obtain database cluster management requirements and to create a description file based on those requirements. Add a module to create a container image of the database to be managed, and add a bootstrapping component to the image database. The bootstrapping component is used to assign roles to the cluster nodes of the database to be managed under different architectures. The synchronization module is used to determine the cluster master database and cluster standby database in the mirror database according to the bootstrapping component, and to perform cluster data synchronization, including: sorting the database containers of the mirror database through the bootstrapping component, determining the cluster master database and cluster standby database in the mirror database according to the database container sorting result; backing up the data of the cluster master database, and synchronizing the data of the cluster standby database according to the data backup of the cluster master database. The management module is used to manage the database architecture of the mirror database after data synchronization according to the description file; The description file includes the number of replicas; the step of sorting the database containers of the image database through the bootstrap component, and determining the cluster master and cluster standby databases in the image database based on the database container sorting result, includes: Based on the bootstrap component, the mirror database is sorted into database containers according to the number of replicas; Set the database cluster corresponding to the first database container in the sort order as the cluster master database, and set the remaining database clusters as cluster slave databases. The step of backing up the data in the cluster master database and synchronizing the data in the cluster standby database based on the data backup of the cluster master database includes: The bootstrapping component performs data backup on the cluster master database and modifies the external interface status of the cluster master database to allow external access. The cluster backup database polls the external interface of the cluster master database. When the external interface status of the cluster master database is allowed to access the outside world, the cluster backup database downloads the data backup of the cluster master database and modifies the external interface status of the cluster backup database to be allowed to access the outside world, until the external interface status of all the cluster backup databases is allowed to access the outside world.
6. An electronic device, characterized in that, Including memory and processor, among which, The memory is used to store programs; The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the database cluster management method of any one of claims 1 to 4.
7. A computer-readable storage medium, characterized in that, Used to store computer-readable programs or instructions, which, when executed by a processor, are capable of implementing the steps in the database cluster management method of any one of claims 1 to 4.
Citation Information
Patent Citations
Cluster management method and device and electronic equipment
CN115373799A
Cluster creation using self-aware, self-joining cluster nodes
US20190394093A1