CN112416515A - Method, system, equipment and medium for deploying Keepalived cluster - Google Patents
Method, system, equipment and medium for deploying Keepalived cluster Download PDFInfo
- Publication number
- CN112416515A CN112416515A CN202011306094.7A CN202011306094A CN112416515A CN 112416515 A CN112416515 A CN 112416515A CN 202011306094 A CN202011306094 A CN 202011306094A CN 112416515 A CN112416515 A CN 112416515A
- Authority
- CN
- China
- Prior art keywords
- node
- configuration file
- file template
- cluster
- setting
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000013515 script Methods 0.000 claims abstract description 45
- 230000003247 decreasing effect Effects 0.000 claims description 8
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000009434 installation Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a method, a system, equipment and a storage medium for deploying a keepalive cluster, wherein the method comprises the following steps: setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template; setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template; adding a state switching script in a standby node configuration file template to switch states when a main node fails; and sequentially logging in each node in the cluster, copying the master node configuration file template and the standby node configuration file template to the corresponding node, and starting a keepalive service of the corresponding node. According to the invention, different weight values are set in the configuration file, so that the standby nodes can be automatically switched according to the weight values when the main node in the cluster fails.
Description
Technical Field
The present invention relates to the field of cluster deployment, and more particularly, to a method, a system, a computer device, and a readable medium for Keepalived cluster deployment.
Background
The Keepalived software is a common server high-availability open source software and can be used for preventing single-point failure of the server. At least two to a plurality of server nodes are deployed to form a cluster so as to provide the function of switching to a standby node when a high availability fault is provided. The keepalive cluster configuration needs to select a master role master node and a plurality of backup role standby nodes, the prior art needs to log in server nodes one by one for installation configuration, and when the cluster nodes are more, the time is long. In addition, in the prior art, when the main node fails, no method is available for quickly determining a new main node in the standby node, which seriously affects the performance of software.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide a method, a system, a computer device, and a computer-readable storage medium for deploying keepalive clusters, where a basic configuration file template and a state switching script are set, so that one-key deployment can be performed, and deployment time is greatly saved; in addition, different weight values are set in the basic configuration file template, so that the standby nodes can be automatically switched according to the weight values when the main node in the cluster fails, and the performance of the cluster is enhanced.
Based on the above object, an aspect of the embodiments of the present invention provides a method for deploying Keepalived clusters, including the following steps: setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template; setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template; adding the state switching script into the standby node configuration file template so as to switch states when a main node fails; and sequentially logging in each node in the cluster, copying the main node configuration file template and the standby node configuration file template to the corresponding node, and starting the keepalive service of the corresponding node.
In some embodiments, said setting a different weight value in each of said base profile templates comprises: and sequentially decreasing the weight value configured in each basic configuration file template.
In some embodiments, the setting of the basic configuration file template and the state switching script of the Keepalived cluster deployment includes: and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
In some embodiments, the method further comprises: responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
In another aspect of the embodiments of the present invention, a Keepalived cluster deployment system is further provided, including: the system comprises a setting module, a state switching module and a dynamic configuration module, wherein the setting module is used for configuring basic configuration file templates and state switching scripts for setting keepalive cluster deployment, and setting different weight values in each basic configuration file template; the role module is configured to set a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and set a standby node role in other basic configuration file templates to form a standby node configuration file template; the switching module is configured to add the state switching script into the standby node configuration file template so as to switch states when a main node fails; and the execution module is configured to log in each node in the cluster in sequence, copy the master node configuration file template and the standby node configuration file template to the corresponding node, and start the keepalive service of the corresponding node.
In some embodiments, the setup module is configured to: and sequentially decreasing the weight value configured in each basic configuration file template.
In some embodiments, the setup module is configured to: and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
In some embodiments, the setup module is configured to: responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
In another aspect of the embodiments of the present invention, there is also provided a computer device, including: at least one processor; and a memory storing computer instructions executable on the processor, the instructions when executed by the processor implementing the steps of the method as above.
In a further aspect of the embodiments of the present invention, a computer-readable storage medium is also provided, in which a computer program for implementing the above method steps is stored when the computer program is executed by a processor.
The invention has the following beneficial technical effects: by setting the basic configuration file template and the state switching script, one-key deployment can be realized, and the deployment time is greatly saved; in addition, different weight values are set in the basic configuration file template, so that the standby nodes can be automatically switched according to the weight values when the main node in the cluster fails, and the performance of the cluster is enhanced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
Fig. 1 is a schematic diagram of an embodiment of a Keepalived cluster deployment method provided in the present invention;
fig. 2 is a schematic hardware structure diagram of an embodiment of a computer device deployed by a Keepalived cluster provided in the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
Based on the above purpose, a first aspect of the embodiments of the present invention provides an embodiment of a Keepalived cluster deployment method. Fig. 1 is a schematic diagram illustrating an embodiment of a Keepalived cluster deployment method provided in the present invention. As shown in fig. 1, the embodiment of the present invention includes the following steps:
s1, setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template;
s2, setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template;
s3, adding a state switching script in the standby node configuration file template to switch states when the main node fails; and
and S4, sequentially logging in each node in the cluster, copying the main node configuration file template and the standby node configuration file template to the corresponding nodes, and starting the keepalive service of the corresponding nodes.
According to the embodiment of the invention, keepalive software can be automatically installed on a plurality of nodes by one key, different main and standby roles and weight values are configured at the same time, and the script triggered when the keepalive main and standby nodes are switched is automatically copied and distributed, so that the one-key installation of the keepalive cluster is realized, the deployment cost is greatly saved, and the complicated and fussy deployment operation is simplified, systematized and normalized.
Setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template. Variables to be configured in the basic configuration file template include PRIORITY _ X (weight), INTERFACE _ X (network card name bound), STATE _ X (node role MASTER or BACKUP), VRID _ X (cluster id randomly gets id of 0-255).
In some embodiments, said setting a different weight value in each of said base profile templates comprises: and sequentially decreasing the weight value configured in each basic configuration file template. A maximum weight value may be set in the first base profile template, after which the weight values in each base profile template are decremented by the same magnitude. For example, a maximum weight value of 100 is set in the first base profile template, a weight value of 98 in the second base profile template, a weight value of 96 in the third base profile template, and so on.
In other embodiments, the weight value configured in each basic profile template may be sequentially increased. Setting the weight values in order can determine a new master node in the standby nodes most quickly when the master node fails. However, this is not a limitation on the weight value, and only technical solutions that can make the weight value in each basic profile template different belong to the scope of protection of the present application.
In some embodiments, the setting of the basic configuration file template and the state switching script of the Keepalived cluster deployment includes: and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
In some embodiments, the method further comprises: responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node. When monitoring that the current main node fails, the state switching script can judge whether the weight value of the current node is the maximum value in the cluster, if the weight value of the current node is the maximum value in the cluster, the current node is switched to the main node, and if the weight value of the current node is not the maximum value in the cluster, the role and the state of the current node are not changed.
And setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template.
And adding a state switching script in the standby node configuration file template to switch states when the main node fails. The state switching script can be added into the standby node configuration file, and can also be directly copied into the node. And copying an executable script triggered by the node switching to a MASTER state and a BACKUP state according to a specified directory (/ usr/local/ism/sysmgt/sbin /) configured in the node template. In other embodiments, a status switching script may be added to each node, so that a failed master node may be switched to a failure status as soon as possible.
Sequentially logging in each node in the cluster, copying the master node configuration file template and the standby node configuration file template to the corresponding nodes, and starting the keepalive service of the corresponding nodes. And automatically logging in each node in the cluster in sequence through an ssh command, copying the installation package and the keepalive configuration file template into the node, and starting the keepalive service on the node.
The installation package and the keepalive configuration file template are copied to the nodes by sequentially and automatically logging in each node in the cluster through ssh (Secure Shell) commands, the default roles of the nodes in the template file are replaced, the weight values are sequentially decreased, and the same node weight is avoided. And copying a script triggered by switching to the node, and starting the keepalive service on the node to run. The method realizes one-key installation of the Keepalived cluster, greatly saves the deployment cost, and simplifies, systematizes and standardizes the complex and fussy deployment operation. The keepalive software can be automatically installed on a plurality of nodes by one key, different main and standby roles and weight values are configured at the same time, and scripts triggered when the keepalive main and standby nodes are switched are automatically copied and distributed.
It should be particularly noted that, steps in the above methods for keepalive cluster deployment may be mutually intersected, replaced, added, and deleted, and therefore, these methods for keepalive cluster deployment that are transformed by reasonable permutation and combination also belong to the scope of the present invention, and the scope of the present invention should not be limited to the embodiments.
Based on the above object, a second aspect of the embodiments of the present invention provides a Keepalived cluster deployment system, including: the system comprises a setting module, a state switching module and a dynamic configuration module, wherein the setting module is used for configuring basic configuration file templates and state switching scripts for setting keepalive cluster deployment, and setting different weight values in each basic configuration file template; the role module is configured to set a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and set a standby node role in other basic configuration file templates to form a standby node configuration file template; the switching module is configured to add the state switching script into the standby node configuration file template so as to switch states when a main node fails; and the execution module is configured to log in each node in the cluster in sequence, copy the master node configuration file template and the standby node configuration file template to the corresponding node, and start the keepalive service of the corresponding node.
In some embodiments, the setup module is configured to: and sequentially decreasing the weight value configured in each basic configuration file template.
In some embodiments, the setup module is configured to: and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
In some embodiments, the setup module is configured to: responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
In view of the above object, a third aspect of the embodiments of the present invention provides a computer device, including: at least one processor; and a memory storing computer instructions executable on the processor, the instructions being executable by the processor to perform the steps of: s1, setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template; s2, setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template; s3, adding a state switching script in the standby node configuration file template to switch states when the main node fails; and S4, sequentially logging in each node in the cluster, copying the main node configuration file template and the standby node configuration file template to the corresponding nodes, and starting the keepalive service of the corresponding nodes.
In some embodiments, said setting a different weight value in each of said base profile templates comprises: and sequentially decreasing the weight value configured in each basic configuration file template.
In some embodiments, the setting of the basic configuration file template and the state switching script of the Keepalived cluster deployment includes: and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
In some embodiments, the steps further comprise: responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
Fig. 2 is a schematic hardware structural diagram of an embodiment of a computer device deployed for the Keepalived cluster provided in the present invention.
Taking the apparatus shown in fig. 2 as an example, the apparatus includes a processor 301 and a memory 302, and may further include: an input device 303 and an output device 304.
The processor 301, the memory 302, the input device 303 and the output device 304 may be connected by a bus or other means, and fig. 2 illustrates the connection by a bus as an example.
The memory 302 is used as a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the Keepalived cluster deployment method in the embodiment of the present application. The processor 301 executes various functional applications of the server and data processing by running the nonvolatile software program, instructions and modules stored in the memory 302, that is, implements the Keepalived cluster deployment method of the above method embodiment.
The memory 302 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created from use of a method deployed by Keepalived clusters, and the like. Further, the memory 302 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 embodiments, memory 302 optionally includes memory located remotely from processor 301, which may be connected to a local module via 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 303 may receive information such as a user name and a password that are input. The output means 304 may comprise a display device such as a display screen.
Program instructions/modules corresponding to one or more keepalive cluster deployment methods are stored in the memory 302 and, when executed by the processor 301, perform the keepalive cluster deployment methods in any of the above-described method embodiments.
Any embodiment of a computer device executing the method for Keepalived cluster deployment described above may achieve the same or similar effects as any of the preceding method embodiments corresponding thereto.
The invention also provides a computer readable storage medium storing a computer program which, when executed by a processor, performs the method as above.
Finally, it should be noted that, as one of ordinary skill in the art can appreciate that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program to instruct relevant hardware, and the programs of the Keepalived cluster deployment method can be stored in a computer readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium of the program may be a magnetic disk, an optical disk, a Read Only Memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described method embodiments.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A method for Keeplived cluster deployment is characterized by comprising the following steps:
setting basic configuration file templates and state switching scripts for Keeplived cluster deployment, and setting different weight values in each basic configuration file template;
setting a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and setting a standby node role in other basic configuration file templates to form a standby node configuration file template;
adding the state switching script into the standby node configuration file template so as to switch states when a main node fails; and
sequentially logging in each node in the cluster, copying the main node configuration file template and the standby node configuration file template to the corresponding node, and starting the keepalive service of the corresponding node.
2. The method of claim 1, wherein setting different weight values in each of the base profile templates comprises:
and sequentially decreasing the weight value configured in each basic configuration file template.
3. The method of claim 1, wherein setting a base configuration file template and a state switching script for a Keepalived cluster deployment comprises:
and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
4. The method of claim 3, further comprising:
responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and
and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
5. A system for Keeplived cluster deployment, comprising:
the system comprises a setting module, a state switching module and a dynamic configuration module, wherein the setting module is used for configuring basic configuration file templates and state switching scripts for setting keepalive cluster deployment, and setting different weight values in each basic configuration file template;
the role module is configured to set a main node role in the basic configuration file template with the maximum weight value to form a main node configuration file template, and set a standby node role in other basic configuration file templates to form a standby node configuration file template;
the switching module is configured to add the state switching script into the standby node configuration file template so as to switch states when a main node fails; and
and the execution module is configured to log in each node in the cluster in sequence, copy the master node configuration file template and the standby node configuration file template to the corresponding node, and start the Keepalived service of the corresponding node.
6. The system of claim 5, wherein the setup module is configured to:
and sequentially decreasing the weight value configured in each basic configuration file template.
7. The system of claim 5, wherein the setup module is configured to:
and setting monitoring in the state switching script to monitor whether the current main node fails in real time.
8. The system of claim 7, wherein the setup module is configured to:
responding to the fault of the current main node, and judging whether the weight value of the current node is the maximum value in the cluster or not through a state switching script; and
and responding to the fact that the weight value of the current node is the maximum value in the cluster, and switching the current node into the main node.
9. A computer device, comprising:
at least one processor; and
a memory storing computer instructions executable on the processor, the instructions when executed by the processor implementing the steps of the method of any one of claims 1 to 4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011306094.7A CN112416515A (en) | 2020-11-20 | 2020-11-20 | Method, system, equipment and medium for deploying Keepalived cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011306094.7A CN112416515A (en) | 2020-11-20 | 2020-11-20 | Method, system, equipment and medium for deploying Keepalived cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112416515A true CN112416515A (en) | 2021-02-26 |
Family
ID=74774692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011306094.7A Withdrawn CN112416515A (en) | 2020-11-20 | 2020-11-20 | Method, system, equipment and medium for deploying Keepalived cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416515A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826892A (en) * | 2022-04-28 | 2022-07-29 | 济南浪潮数据技术有限公司 | Cluster node control method, device, equipment and medium |
| CN115757361A (en) * | 2022-12-26 | 2023-03-07 | 北京柏睿数据技术股份有限公司 | Method and system for automatic deployment of database cluster system |
-
2020
- 2020-11-20 CN CN202011306094.7A patent/CN112416515A/en not_active Withdrawn
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826892A (en) * | 2022-04-28 | 2022-07-29 | 济南浪潮数据技术有限公司 | Cluster node control method, device, equipment and medium |
| CN115757361A (en) * | 2022-12-26 | 2023-03-07 | 北京柏睿数据技术股份有限公司 | Method and system for automatic deployment of database cluster system |
| CN115757361B (en) * | 2022-12-26 | 2023-08-18 | 北京柏睿数据技术股份有限公司 | Automatic deployment method and system for database cluster system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109347675B (en) | Server configuration method and device and electronic equipment | |
| CN110389900B (en) | Distributed database cluster testing method and device and storage medium | |
| WO2017162173A1 (en) | Method and device for establishing connection of cloud server cluster | |
| US9037899B2 (en) | Automated node fencing integrated within a quorum service of a cluster infrastructure | |
| CN107404524B (en) | Distributed cluster node access method and device | |
| CN111404924B (en) | Security management and control method, device, equipment and storage medium of cluster system | |
| CN111984274A (en) | Method and device for one-key automatic deployment of ETCD (electronic toll collection) cluster | |
| CN116755794A (en) | Automatic deployment method and system for application program in cloud native | |
| CN112114939A (en) | Distributed system deployment equipment and method | |
| CN112416515A (en) | Method, system, equipment and medium for deploying Keepalived cluster | |
| CN115658390A (en) | Container disaster tolerance method, system, device, equipment and computer readable storage medium | |
| CN112653576B (en) | Network card identification processing method, system, terminal and storage medium based on Kylin system | |
| CN111176904B (en) | Method, system, equipment and medium for data backup under private cloud architecture | |
| CN111813606A (en) | Fault-tolerant method, system, equipment and medium for double-node virtual machine | |
| CN112698979A (en) | Method and device for processing zookeeper double nodes, storage medium and processor | |
| CN112131201B (en) | Method, system, equipment and medium for high availability of network additional storage | |
| CN111884919B (en) | Method, device, equipment and readable medium for clearing invalid virtual IP | |
| CN110704160B (en) | Dual-computer hot standby test method and device | |
| CN115220737A (en) | Mirror image deployment method and device, computer equipment and storage medium | |
| CN111404771A (en) | Network load testing method, device, equipment and medium | |
| CN114553686B (en) | Method, system, equipment and storage medium for switching main and standby flow | |
| CN112003725A (en) | Method, system, device and medium for deploying GPU license server | |
| CN117093425A (en) | Method, system, equipment and storage medium for high availability of database | |
| CN117478299B (en) | Block chain consensus algorithm switching method, device and computer equipment | |
| CN117278414A (en) | Method and device for managing server based on HMC |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210226 |
|
| WW01 | Invention patent application withdrawn after publication |