CN110007934B - Distributed database deployment method and device - Google Patents
Distributed database deployment method and device Download PDFInfo
- Publication number
- CN110007934B CN110007934B CN201910236419.XA CN201910236419A CN110007934B CN 110007934 B CN110007934 B CN 110007934B CN 201910236419 A CN201910236419 A CN 201910236419A CN 110007934 B CN110007934 B CN 110007934B
- Authority
- CN
- China
- Prior art keywords
- database
- node
- deployed
- nodes
- instruction
- 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.)
- Active
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/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/61—Installation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The embodiment of the invention provides a distributed database deployment method and device. The method comprises the following steps: acquiring an installation medium issuing instruction, and issuing an installation medium to a plurality of nodes to be deployed; if the fact that the installation medium is successfully issued to the nodes to be deployed is judged and known, a decompression instruction is sent to the nodes to be deployed, and therefore each node to be deployed installs the database on the node to be deployed; if the fact that the database is successfully installed on the nodes to be deployed is judged and known, the configuration file corresponding to the deployment is issued to the nodes to be deployed, and each node to be deployed configures the installed database; and if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database, issuing a database starting instruction to the plurality of nodes to be started so that each node to be started starts the database. The distributed database deployment method and device provided by the embodiment of the invention can improve the deployment efficiency.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a distributed database deployment method and device.
Background
With the gradual maturity of the traditional database technology, the rapid development of the computer network technology and the expansion of the application range, the research and development of the database system with distributed as the main characteristic are noticed by people. Distributed databases are the product of the combination of database technology and network technology, and have formed an important branch in the field of databases. Since the 90 s of the 20 th century, distributed database systems were in the commercialization phase, traditional relational database products were developed into distributed database products with computer networks and multitask operating systems as cores, and distributed databases gradually developed to client/server mode. With the rise of big data, cloud computing and artificial intelligence, the requirement on installed capacity of a distributed database is higher and higher, the requirement on the number of cluster nodes is higher and higher, the large data platform of a general small-medium enterprise reaches hundreds of nodes, and the large data platform of a large enterprise reaches thousands of database nodes or more.
In the case of deploying a component in a cluster mode, in the prior art, a configuration database is installed through a shell instruction or through an Advanced Packaging Tool, specifically, after a single node is manually logged through an XShell client or a CRT based on an SSH or SFTP technology, the component (an installation source) is uploaded, the component is decompressed through a tar-zxvf xxx (component name) command, tar, gz, the component is decompressed into a directory to change configuration files, for example, vim ds.xml and the like, and then the component is saved and logged out, and a start command is executed, so that the deployment of one node in the cluster is completed, and the remaining nodes need to perform the same step operation.
The existing distributed Database deployment mode needs a Database Administrator (DBA for short) to perform daily tedious and repeated labor, and is long in time, low in efficiency, prone to error and extremely difficult in node maintenance.
Disclosure of Invention
The embodiment of the invention provides a distributed database deployment method and a distributed database deployment device, which are used for solving or at least partially solving the defect of low deployment efficiency in the prior art.
In a first aspect, an embodiment of the present invention provides a distributed database deployment method, including:
acquiring an installation medium issuing instruction, and issuing an installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction;
if the installation medium is judged and known to be successfully issued to the plurality of nodes to be deployed, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and a database is installed on the nodes to be deployed;
if the fact that the database is successfully installed on the plurality of nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, a configuration file corresponding to the current deployment is issued to the plurality of nodes to be deployed according to the configuration file issuing instruction, and each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment;
and if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database according to the configuration file corresponding to the deployment, issuing a database starting instruction to the plurality of nodes to be started so that each node to be started starts the configured database.
In a second aspect, an embodiment of the present invention provides a distributed database deployment apparatus, including:
the installation source issuing module is used for acquiring an installation medium issuing instruction and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction;
the installation source decompression module is used for sending a decompression instruction to the plurality of nodes to be deployed if the installation medium is judged and known to be successfully issued to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and a database is installed on the nodes to be deployed;
the database configuration module is used for acquiring a configuration file issuing instruction if the database is judged to be successfully installed on the plurality of nodes to be deployed, and issuing the configuration file corresponding to the current deployment to the plurality of nodes to be deployed according to the configuration file issuing instruction so that each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment;
and the database starting module is used for issuing a database starting instruction to the plurality of nodes to be started if the plurality of nodes to be deployed are judged to complete the configuration of the installed database according to the configuration file corresponding to the deployment, so that each node to be started starts the configured database.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when executing the computer program, the steps of the distributed database deployment method provided in any one of the various possible implementations of the first aspect are implemented.
In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the distributed database deployment method as provided in any one of the various possible implementations of the first aspect.
The distributed database deployment method and the distributed database deployment device provided by the embodiment of the invention complete the deployment of the distributed database through the unified platform, avoid the one-by-one deployment of the nodes, and particularly greatly shorten the deployment time and greatly improve the deployment efficiency under the condition that the number of the nodes included in the cluster is larger. And by issuing the unified configuration file, the difference error caused by manually configuring the nodes one by one can be avoided, the error in the operation of the distributed database can be reduced, and the nodes can be started more conveniently.
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 some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a distributed database deployment method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a distributed database deployment apparatus provided according to an embodiment of the present invention;
fig. 3 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to overcome the above problems in the prior art, embodiments of the present invention provide a distributed database deployment method and apparatus, and the inventive concept is that a thread concurrent processing manner is adopted, instructions for triggering nodes to execute corresponding operations are concurrently processed in one main control thread, the steps of repeated operations of a plurality of nodes are unified and synchronized, only information of nodes to be deployed and a unified configuration file are required, and the time for deploying a cluster is shortened from the time for sequentially deploying a plurality of nodes to the time for deploying a node, so that the time consumed for deployment is greatly shortened, and the deployment efficiency is improved.
Fig. 1 is a schematic flowchart of a distributed database deployment method according to an embodiment of the present invention. As shown in fig. 1, the method includes: and S101, acquiring an installation medium issuing instruction, and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction.
It should be noted that a distributed database system typically uses smaller computer systems, each of which can be individually located in a single location, each of which may have a complete copy, or a partial copy, of the DBMS, and has its own local database, and many computers located in different locations are interconnected via a network to form a complete, globally logically centralized, physically distributed large database. Each computer is a node, and a plurality of computing mechanisms for forming the database form a cluster.
The execution main body of the distributed database deployment method provided by the embodiment of the invention is a distributed database deployment device. The device is a uniform management operation and maintenance platform and can support uniform configuration and simultaneous installation and deployment of all nodes in a cluster.
The user of the device is typically a database administrator, but is not limited to a database administrator. In the following embodiments of the present invention, a database administrator is taken as an example for description.
And the installation medium issuing instruction is used for triggering the distributed database deployment device to issue the installation medium to the node.
The installation medium (which may be simply referred to as the medium), i.e., the installation source, is a compressed package generated for compressing the multiple components required to deploy the distributed database.
The installation medium may be stored in advance in a storage module of the distributed database deployment apparatus, or may be stored in a storage device connected to the distributed database deployment apparatus.
And the database administrator can input the installation medium to issue the command through the input equipment connected with the distributed database deployment device. For example, the "installation medium issuing" button is clicked by a mouse, a finger, a stylus pen, or the like, and the installation medium issuing instruction is input by inputting a corresponding command by a keyboard or the like.
The installation medium issuing command carries information of an issuing object of the installation medium, namely information of a node which needs to receive the installation medium.
And installing the issued objects of the media, namely a plurality of nodes to be deployed. The plurality of nodes to be deployed are part or all of the nodes to be deployed selected by the database administrator.
Therefore, after the distributed database deployment device obtains the installation medium issuing instruction, the distributed database deployment device can obtain the information of the issuing object according to the installation medium issuing instruction, determine to which nodes the installation medium needs to be issued, and issue the installation medium to the plurality of nodes to be deployed.
For any one of the nodes to be deployed, after the distributed database deployment device issues the installation medium to the node, the node receives the installation medium.
And S102, if the installation medium is successfully issued to the plurality of nodes to be deployed is judged and known, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and the database is installed on the nodes to be deployed.
Specifically, after the installation medium is delivered to the nodes to be deployed, the distributed database deployment apparatus may monitor the delivery progress and the delivery status of the installation medium delivered to the nodes to be deployed, and determine whether each node to be deployed has successfully received the installation medium, that is, determine whether the installation medium has been successfully delivered to the node to be deployed.
The distributed database deployment apparatus may start a monitoring thread for each node to be deployed in the delivered object. In the monitoring thread, the total capacity of the installation medium can be obtained, the size of the issued medium content is obtained once according to preset unit time (such as every second), the real-time issuing rate is calculated, the size of the space occupied by the issued medium content is obtained in real time, the estimated issuing completion time is calculated according to the total capacity of the installation medium, the real-time issuing rate and the size of the space occupied by the issued medium content, and good perception is provided for a database administrator.
According to the total capacity of the installation medium and the space occupied by the issued medium content, the percentage of the space occupied by the issued medium content in the total capacity of the installation medium can be obtained as the issuing progress.
According to the issuing progress, the issuing state can be obtained. If the issuing progress is 0, the issuing state is waiting for issuing; the issuing progress is 100%, and the issuing state is the completion of issuing; and if the issuing progress is not 0 and not 100%, the issuing state is issuing.
If the issuing states of all the nodes to be deployed are completed, that is, the nodes to be deployed all have successfully received the installation medium and the installation medium has been successfully issued to each of the nodes to be deployed, the distributed database deployment apparatus may send the decompression instruction to the nodes to be deployed.
And the decompression instruction is used for triggering the node to be deployed to execute the decompression operation on the installation medium.
After receiving the decompression instruction, the node to be deployed decompresses a plurality of components required for deploying the distributed database in the installation medium to a specified storage position, so that the database is installed on the node to be deployed.
The method may be configured to monitor that after the installation medium is successfully issued to the plurality of nodes to be deployed, the distributed database deployment apparatus automatically sends the decompression instruction to each node in the plurality of nodes to be deployed, or may be configured to monitor that after the installation medium is successfully issued to the plurality of nodes to be deployed, the database administrator inputs the trigger decompression instruction through an input device connected to the distributed database deployment apparatus, and after the distributed database deployment apparatus receives the trigger decompression instruction, the distributed database deployment apparatus sends the decompression instruction to each node in the plurality of nodes to be deployed.
And triggering a decompression instruction, wherein the decompression instruction is used for triggering the distributed database deployment device to issue the decompression instruction to the node to be deployed. And triggering a decompression instruction, namely triggering the distributed database deployment device to issue the decompression instruction to the node to be deployed.
Step S103, if the situation that the database is successfully installed on the plurality of nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, the configuration file corresponding to the current deployment is issued to the plurality of nodes to be deployed according to the configuration file issuing instruction, and therefore each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment.
Specifically, after the decompression instruction is sent to the plurality of nodes to be deployed, the distributed database deployment apparatus may monitor the decompression progress and the decompression state of the decompression installation medium for the plurality of nodes to be deployed, and determine whether the database has been successfully installed on the node to be deployed by determining whether each of the nodes to be deployed has completed pressurization of the installation medium.
The distributed database deployment device can start a new monitoring thread for each node in the plurality of nodes to be deployed, and can also continue to use the monitoring thread for monitoring the issuing progress and the issuing state of the installation medium to monitor the decompressing progress and the decompressing state of the nodes to be deployed.
The decompression progress may be determined as a percentage of the size of the decompressed media content to the total capacity size of the installed media. In the thread, the total capacity of the installation medium can be obtained, the size of the decompressed medium content is obtained once according to preset unit time (such as every second), the real-time decompression rate is calculated, the size of the decompressed medium content is obtained in real time, and the estimated decompression completion time is calculated according to the total capacity of the installation medium and the size of the decompressed medium content, so that a database administrator can be well perceived.
The decompression progress may also be determined as a percentage of the number of decompressed files to the total number of files of the installation medium. In the thread, the total number of files of the installation medium, the real-time decompression rate and the number of decompressed files can be obtained, and the estimated decompression completion time is calculated according to the total number of files of the installation medium, the real-time decompression rate and the number of decompressed files, so that a database administrator is provided with good perception.
According to the decompression progress, the decompression state can be acquired. When the decompression progress is 0, the decompression state is a state of waiting for decompression; when the decompression progress is 100%, the decompression state is decompression completion; when the decompression progress is not 0 and not 100%, the decompression state is decompression.
After decompression is completed, the database is successfully installed on the node to be deployed; otherwise, the database has not been successfully installed on the node to be deployed.
And if the decompression states of all the nodes in the plurality of nodes to be deployed are decompression completed, namely the plurality of nodes to be deployed are successfully provided with the database, acquiring the configuration file and issuing the instruction.
And the configuration file issuing instruction is used for triggering the distributed database deployment device to issue the configuration file corresponding to the deployment to the node to be deployed.
The corresponding configuration file for the deployment can be generated in advance according to the configuration of the database administrator on the cluster parameters.
And the database administrator can input the configuration file issuing instruction through the input equipment connected with the distributed database deployment device. For example, a "profile issue" button is clicked by a mouse, a finger, a stylus, or the like, and a profile issue instruction is input by inputting a corresponding command by a keyboard or the like.
After receiving the configuration file issuing instruction, the distributed database deployment device acquires the configuration file corresponding to the deployment according to the instruction, and issues the configuration file corresponding to the deployment to the plurality of nodes to be deployed.
For any one node in the nodes to be deployed, after the distributed database deployment device issues the configuration file corresponding to the deployment to the node, the node receives the configuration file corresponding to the deployment.
It should be noted that the installation medium includes a default configuration file in addition to a plurality of components required for deploying the distributed database. In the upgrading and deploying process of the distributed database, due to the change of the database version, the configuration later may be different from the configuration in the default configuration file, so for the installation medium issued in the deploying process and the database installed according to the installation medium, configuration needs to be performed according to the configuration file corresponding to the deploying.
For any one of the nodes to be deployed, after receiving the configuration file corresponding to the current deployment, the node changes and stores the information in the default configuration file according to the configuration file corresponding to the current deployment, and completes the configuration of the database installed at this time.
Step S104, if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database according to the configuration file corresponding to the deployment, a database starting instruction is issued to the plurality of nodes to be started, so that each node to be started starts the database which is configured.
Specifically, after the configuration file corresponding to the deployment is issued to the plurality of nodes to be deployed, the distributed database deployment apparatus may determine whether the plurality of nodes to be deployed complete the configuration of the installed database according to the configuration file corresponding to the deployment.
Because the time consumed for changing and storing the information in the default configuration file is short according to the configuration file corresponding to the deployment, the issuing state of the configuration file corresponding to the deployment can be issued to the plurality of nodes to be deployed and can be used as a basis for judging whether the configuration of the installed database is completed.
The distributed database deployment device can start a new monitoring thread for each node to be deployed in the issued object, and can also continue to use the monitoring threads for monitoring the decompression progress and the decompression state of the installation medium to monitor the issuing progress and the issuing state of the configuration file corresponding to the deployment of the node to be deployed.
In the monitoring thread, the size of the space occupied by the configuration file corresponding to the deployment can be obtained, the size of the content of the issued configuration file is obtained once according to preset unit time (such as every second), the real-time issuing rate is calculated, the size of the space occupied by the content of the issued configuration file is obtained in real time, and the estimated issuing completion time is calculated according to the size of the space occupied by the configuration file corresponding to the deployment, the real-time issuing rate and the size of the space occupied by the content of the issued configuration file, so that a database administrator is well perceived.
According to the size of the space occupied by the configuration file corresponding to the deployment and the size of the space occupied by the content of the issued configuration file, the percentage of the size of the space occupied by the content of the issued configuration file to the size of the space occupied by the configuration file corresponding to the deployment can be obtained and used as the issuing progress.
And acquiring the issuing state according to the issuing progress. If the issuing progress is 0, the issuing state is waiting for issuing; the issuing progress is 100%, and the issuing state is the completion of issuing; and if the issuing progress is not 0 and not 100%, the issuing state is issuing.
If the issuing state is that the issuing is finished, the configuration of the installed database can be considered to be finished; otherwise, the configuration of the installed database may be considered incomplete.
If each node in the plurality of nodes to be deployed has completed configuring the database installed on the node according to the configuration file corresponding to the deployment, the distributed database deployment apparatus may issue a database start instruction to the plurality of nodes to be started.
It is understood that for all nodes to be deployed with completed database configuration, some or all of the installed databases of the nodes may be started to complete the deployment of the distributed database.
And the database starting instruction is used for triggering the node to be started to start the configured database installed on the node.
The distributed database deployment apparatus may be configured to automatically send a database start instruction to each of the plurality of nodes to be deployed after monitoring that each of the plurality of nodes to be deployed has completed configuring the database according to the configuration file corresponding to the deployment of this time. It is understood that, in this case, the nodes to be deployed are all nodes to be started.
The method may further include monitoring that after each of the plurality of nodes to be deployed completes configuration of the database according to the configuration file corresponding to the deployment, the database administrator inputs a trigger start instruction through an input device connected to the distributed database deployment apparatus, and after receiving the trigger start instruction, the distributed database deployment apparatus issues the database start instruction to the plurality of nodes to be started according to the trigger start instruction.
The database administrator can input the triggering starting instruction through an input device connected with the distributed database deployment device. For example, a "database start" button is clicked by a mouse, a finger, a stylus, or the like, and a trigger start instruction is input by inputting a corresponding command by a keyboard or the like.
And triggering a starting instruction, wherein the starting instruction carries information of the node to be started. The nodes to be started may be all or part of the nodes to be deployed. The database administrator can start all or part of the nodes to be deployed according to the needs, so that the resources of the machines in the cluster can be utilized more reasonably.
After the distributed database deployment device obtains the trigger start instruction, the distributed database deployment device can obtain the information of the nodes to be started according to the database start instruction, and sends the database start instruction to each node to be started.
For any node to be started, SSH connection is established between the distributed database deployment device and the node, and a database starting instruction is issued; after receiving a database starting instruction issued by a distributed database deployment device, the node starts a configured database installed on the node according to the database starting instruction, and can generate a starting log; the distributed database deployment device can obtain the starting log of the node, analyze the rcode file to obtain the starting state mark of the node (the starting state mark at the moment represents starting), and monitor the starting progress and the starting state of the database.
After each node to be started starts the configured database installed on the node, the deployment of the distributed database is completed.
It should be noted that the shell instruction or the Advanced Packaging Tool is based on a Linux environment, but the deployment method provided by the embodiment of the present invention enables non-Linux technicians to install and manage the distributed database through the distributed database deployment device.
The embodiment of the invention finishes the deployment of the distributed database through a unified platform, avoids the one-by-one deployment of the nodes, and particularly can greatly shorten the deployment time and greatly improve the deployment efficiency under the condition that the cluster comprises a large number of nodes. Furthermore, by issuing the unified configuration file, difference errors caused by manually configuring the nodes one by one can be avoided, and errors in the operation of the distributed database can be reduced; through the progress monitoring of each step, errors in the deployment process can be reduced, and the deployment efficiency can be further improved; the nodes can be started more conveniently by uniformly issuing the database starting instruction.
Based on the content of the above embodiments, before acquiring the configuration file issuing instruction, the method further includes: and acquiring a parameter configuration instruction, and generating a temporary configuration file according to the parameter configuration instruction.
Specifically, before the configuration file is obtained and the command is issued, the database administrator may input the parameter configuration command through the input device connected to the distributed database deployment apparatus.
And the parameter configuration instruction is used for setting the values of part or all of the parameters of the distributed database to be deployed. Each parameter is a configuration item or a data item.
The number of parameters of the distributed database is many, and can reach more than hundreds. For example, parameters of the distributed database may include:
the Zookeeper server connection information zk _ server,
the Zookeeper connection lease timeout zk _ leaseTimeout,
the cluster name cluster _ name is the name of the cluster,
the minimum time interval trans _ purge _ time _ interval for which transactions that have committed clear,
the invalid data cleaning interval purge _ lag,
the number of query retry times retry out of mem times limit prefix for insufficient memory in a phase,
the size of the single UNDO log file limits the UNDO log file size,
the maximum cpu core number num _ cores,
whether the Page compression optimization no _ Page _ compression _ optimization is disabled,
the node statistics update period nodestate _ statistics _ cycle,
the percentage lob _ delete _ factor of the allowed number of lob garbage rows to the total number of lob rows,
whether the cost of the Prepare stage is checked to be consistent with the check _ cost of the actual application resource number,
the communication address network _ host,
the single-process concurrent peer-to-peer sub-schedule number current task ratio,
using the prefix _ vs _ composition ratio in the memory of the prefix region occupancy,
the internal communication port inter _ port,
the external communication port session _ port,
IO single buffer maximum read size max _ buffer _ size,
IO thread timeout end time thread timeout,
the number of the sub-buckets of the LLVM cache is LLVM _ cache _ num _ shared _ bits, and the like.
According to the parameter configuration instruction, the parameter value set this time can be obtained, and a temporary configuration file is generated according to the parameter value set this time.
It can be understood that, if the parameter configuration instruction is not acquired before the configuration file issuing instruction is acquired, which indicates that part or all of the parameters of the distributed database are not reset, the configuration file corresponding to the last deployment may be used as the configuration file corresponding to the current deployment.
And generating a configuration file corresponding to the deployment according to the temporary configuration file and the configuration file corresponding to the last deployment.
It should be noted that, after the configuration file corresponding to each deployment is generated, the file may be backed up.
For the deployment, after a temporary configuration file is generated, the file contents of the temporary configuration file and the backed-up configuration file corresponding to the deployment of the last time are automatically compared, and parameters are merged according to a comparison result to generate the configuration file corresponding to the deployment of the current time.
The embodiment of the invention can avoid repeated labor, improve deployment efficiency and update configuration more conveniently by comparing and combining the parameters of the database.
Based on the content of each embodiment, the specific step of generating the configuration file corresponding to the current deployment according to the temporary configuration file and the configuration file corresponding to the last deployment includes: configuring the value of the parameter in the configuration file corresponding to the deployment at this time as the value of the parameter in the temporary configuration file for any parameter in the temporary configuration file; and for any parameter in the configuration file corresponding to the last deployment, if the parameter does not exist in the temporary configuration file, configuring the value of the parameter in the configuration file corresponding to the current deployment as the value of the parameter in the configuration file corresponding to the last deployment.
It will be appreciated that in the temporary configuration file, the values of some of the parameters may be reset.
The specific steps of comparing and merging the file contents of the temporary configuration file and the backed-up configuration file corresponding to the last deployment comprise:
for any parameter in the temporary configuration file, it is described that the value of the parameter is reset, so that in the configuration file corresponding to the deployment this time, the value of the parameter is configured as the value of the parameter in the temporary configuration file; for a parameter that exists in the configuration file corresponding to the last deployment and does not exist in the temporary configuration file, it is described that the value of the parameter is not reset, and therefore, in the configuration file corresponding to the current deployment, the value of the parameter is configured to be the value of the parameter in the configuration file corresponding to the last deployment.
It should be noted that, whether the parameter exists in the configuration file or the temporary configuration file corresponding to the last deployment is determined by the parameter name.
According to the embodiment of the invention, the configuration file corresponding to the deployment is generated by reserving the values of the parameters which are not reset and modifying the values of the reset parameters into new values, so that the repeated labor can be avoided and the deployment efficiency can be improved.
Based on the content of the foregoing embodiments, after issuing the database start instruction to the multiple nodes to be started, the method further includes: and acquiring a trigger stop instruction, and issuing the database stop instruction to a plurality of nodes to be stopped according to the trigger stop instruction so that each node to be stopped stops the operation of the database.
Specifically, when the running of the started database on the plurality of nodes needs to be stopped as required, a database administrator can input a trigger stop instruction through an input device connected with the distributed database deployment device, and after the distributed database deployment device receives the trigger stop instruction, the database stop instruction is issued to the plurality of nodes to be stopped according to the trigger stop instruction.
The database administrator can input the trigger stop instruction through an input device connected with the distributed database deployment device. For example, a "database stop" button is clicked by a mouse, a finger, a stylus pen, or the like, and a trigger stop instruction is input by inputting a corresponding command by a keyboard or the like.
And triggering a stopping instruction, wherein the stopping instruction carries information of the node to be stopped. The nodes to be stopped may be all or some of the nodes that have started.
After the distributed database deployment device obtains the trigger stop instruction, the distributed database deployment device may obtain information of the nodes to be stopped according to the database stop instruction, and issue the database stop instruction to each node to be stopped.
For any node to be stopped, SSH connection is established between the distributed database deployment device and the node, and a database stop instruction is issued; after the node receives a database stopping instruction issued by the distributed database deployment device, the operation of the configured database installed on the node is stopped according to the database stopping instruction, and a stopping log can be generated; the distributed database deployment device can obtain a stop log of the node, analyze the rcode file to obtain a start state mark of the node (the start state mark at this time represents stop), and monitor the stop progress and stop state of the database.
The embodiment of the invention can greatly shorten the time consumption and greatly improve the operation and maintenance efficiency by uniformly stopping the operation of the nodes through the platform, and can more conveniently stop the nodes by uniformly issuing the database starting instruction.
Based on the content of the foregoing embodiments, after issuing the database start instruction to the multiple nodes to be started, the method further includes: and acquiring the running state of each node, and if judging that the running state of any node is abnormal, sending a restart instruction to the node so as to start the configured database after the node is restarted.
Specifically, after at least one node to be started starts the database on the node, the distributed database deployment apparatus may monitor the operating state of each node.
In the monitoring process, firstly, the running state of each node is obtained, for example, the ZooKeeper can be connected through a monitoring process, and whether the registration state of each node is normal or not is determined by inquiring the ZooKeeper in real time.
ZooKeeper is a distributed, open source distributed application coordination service. The ZooKeeper can be used as a registration center, and if a service provider (node) can normally provide database service, the ZooKeeper is registered in the ZooKeeper, and the registration state is registered; if the service provider (node) cannot normally provide the database service, the node is not registered in the ZooKeeper, and the registration state is unregistered. Therefore, the registration state of the node indicates whether the database installed on the node normally provides a service.
It can be understood that, for any node, the registration state of the node in the ZooKeeper may be compared with the start state flag of the node acquired by the distributed database deployment apparatus, and if the two are consistent, the operation state of the node is normal; if the two are not consistent, the operation state of the node is abnormal.
For example, the start state flag of a node indicates start, if the registration state of the node in the ZooKeeper is registered, it indicates that the database on the node is normally running, and the running state of the node is normal when the registration state of the node is consistent with the start state flag; if the registration state of the node in the ZooKeeper is unregistered, the fact that the database on the node normally operates but does not normally operate indicates that the database on the node is shut down and is inconsistent with the start state mark, and the operation state of the node is abnormal; the starting state mark of a certain node indicates stop, if the registration state of the node in the ZooKeeper is unregistered, the database on the node is not operated, the operation state is consistent with the starting state mark, and the operation state of the node is normal; if the registration state of the node in the ZooKeeper is registered, it indicates that the database on the node should stop running but not stop running, there may be a case that the database on the node is artificially and separately started without passing through the distributed database deployment device, and the start state flag is inconsistent with the database on the node, and the running state of the node is abnormal.
If the running state of any node is abnormal, the distributed database deployment device can send a restart instruction to the node and record a restart log.
And the restarting instruction is used for triggering the node to restart and starting the installed database on the node after the restarting is completed. It will be appreciated that at this point, the installed database on the node has completed configuration.
And after receiving the restart instruction, the node is restarted according to the restart instruction, and the installed database on the node is started after the restart is completed.
If the running state of any node is abnormal, the distributed database deployment device can also acquire the running logs of the node, analyze the running logs of the node, and accurately diagnose to solve the problems of the node by analyzing and acquiring the downtime reason, so that a database administrator can maintain the node conveniently, and the maintenance efficiency is improved.
The embodiment of the invention automatically restarts the abnormal nodes and the databases on the abnormal nodes by monitoring the running states of the nodes, so that a database administrator does not need to constantly judge whether the databases are abnormal, and the operation and maintenance efficiency can be improved.
Based on the content of the foregoing embodiments, after issuing the database start instruction to the multiple nodes to be started, the method further includes: and monitoring the running state of the database deployed by each node, and sending an alarm if judging that the running state of the database deployed by any node is abnormal.
Specifically, after at least one node to be started starts the database on the node, the distributed database deployment device may monitor the operating state of each node, and may also monitor the operating state of the database deployed by each node, and determine whether the operating state of the database is normal.
For a database deployed by any node, if the running state of the database is stopped, the running state of the node is only required to be judged, and the database is restarted when the running state is abnormal; if the running state is starting, at least one of the indexes of the node, such as CPU occupancy rate, memory occupancy rate, average response time and the like, can be obtained, and whether the running state of the database deployed at the point is normal or not is judged through the obtained indexes.
If one of the indexes of the node, such as the CPU occupancy rate, the memory occupancy rate, the average response time and the like, exceeds a preset threshold value, the running state of the database deployed by the node is determined to be abnormal, an alarm can be given in an acoustic and/or optical mode, and a database administrator can be informed through one or more of short messages, mails and instant communication messages.
The monitoring and alarming of 7 x 24 hours can be realized through the process, and the health report of the distributed database system can be generated regularly.
According to the embodiment of the invention, the running state of the database deployed by each node is monitored, and the alarm is sent out when the running state is abnormal, so that self-diagnosis and abnormal timely alarm can be realized, better experience is improved for users, and the operation and maintenance efficiency can be improved.
Based on the content of the above embodiments, before obtaining the installation medium issuing instruction, the method further includes: acquiring the environment configuration of each node; and if the environment configuration of any node is judged and learned to meet the deployment requirement of the database, determining the node as the node to be deployed.
Specifically, before the installation medium issuing instruction is acquired, the distributed database deployment device may detect whether each node in the cluster meets the requirement of the installation environment, that is, perform installation environment detection.
And acquiring the user name and the password of each node input by the database administrator. And the user name and the password of the node are used for logging in the node.
For any node, after logging in the node according to the user name and the password of the node, the distributed database deployment device acquires the environment configuration of the node.
The environment configuration of the node at least comprises: one of the indexes of port, operating system version, memory size, CPU core number, disk space size, network performance and the like.
After the environment configuration of the node is obtained, whether the environment configuration of the node meets the minimum requirement for deploying the distributed database is judged. The minimum requirement for deploying a distributed database is the deployment requirement of the database.
If yes, determining the node as a node to be deployed; if not, the installation environment detection result of the node can be generated. The installation environment detection result of the node can be used for prompting a database manager which part of the environment configuration of the node does not accord with the deployment requirement of the database, so that the database manager can ensure that the environment configuration of the node accords with the deployment requirement of the database by replacing a complete machine or upgrading software and hardware configuration.
According to the embodiment of the invention, before the installation medium is obtained to issue the instruction, the installation environment detection is carried out on each node, and the node meeting the deployment requirement of the database is determined as the node to be deployed, so that the error caused by deploying the database on the node not meeting the deployment requirement of the database can be avoided, the deployment efficiency can be improved, and the meaningless resource consumption can be avoided.
It should be noted that, in each embodiment, the detection of the installation environment of each of the multiple nodes, the issuance of the installation medium, the issuance of the decompression instruction, the issuance of the configuration file corresponding to the current deployment, the startup of the database, the stop of the database, the restart of the node and the database, and the like can all be completed by one key, and the deployment process is controlled based on Java implementation; the condition of the current component and the condition of the host can be monitored, all monitoring can be displayed in the same window, the monitoring and displaying of the deployment process are realized based on HTML, CSS or JavaScript and the like, and the activity state of the node component is intuitively obtained; therefore, a database administrator can be liberated from heavy and repeated work in a one-key operation visual guide mode, the work efficiency of the database DBA is improved, and errors caused by excessive manual operation are reduced.
Fig. 2 is a schematic structural diagram of a distributed database deployment apparatus according to an embodiment of the present invention. Based on the content of the foregoing embodiments, as shown in fig. 2, the apparatus includes an installation source issuing module 201, an installation source decompressing module 202, a database configuration module 203, and a database starting module 204, where:
the installation source issuing module 201 is configured to acquire an installation medium issuing instruction, and issue an installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction;
the installation source decompression module 202 is configured to send a decompression instruction to the multiple nodes to be deployed if it is determined that the installation medium is successfully issued to the multiple nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and installs the database on the node to be deployed;
the database configuration module 203 is configured to, if it is determined that the database is successfully installed on the multiple nodes to be deployed, obtain a configuration file issuing instruction, and issue the configuration file corresponding to the current deployment to the multiple nodes to be deployed according to the configuration file issuing instruction, so that each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment;
the database starting module 204 is configured to, if it is determined that all of the plurality of nodes to be deployed have completed configuring the installed database according to the configuration file corresponding to the deployment, issue a database starting instruction to the plurality of nodes to be started, so that each node to be started starts the configured database.
Specifically, the installation source issuing module 201 obtains an installation medium issuing instruction, and issues an installation medium to a plurality of nodes to be deployed according to a plurality of nodes to be deployed selected by the installation medium issuing instruction.
After the installation source issuing module 201 issues the installation medium to the plurality of nodes to be deployed, any one node of the plurality of nodes to be deployed receives the installation medium.
The installation source decompression module 202 determines whether the installation medium has been successfully delivered to all the nodes in the plurality of nodes to be deployed, and sends a decompression instruction to the plurality of nodes to be deployed if the determination result is yes.
After receiving the decompression instruction, the node to be deployed decompresses a plurality of components required for deploying the distributed database in the installation medium to a specified storage position, so that the database is installed on the node to be deployed.
The database configuration module 203 determines whether all the nodes in the plurality of nodes to be deployed have completed the installation of the database, and if yes, acquires a configuration file issuing instruction, acquires a configuration file corresponding to the deployment according to the instruction, and issues the configuration file corresponding to the deployment to the plurality of nodes to be deployed.
And after receiving the configuration file corresponding to the current deployment, the node to be deployed changes and stores the information in the default configuration file according to the configuration file corresponding to the current deployment, so as to complete the configuration of the database installed at this time.
The database starting module 204 determines whether all the nodes in the plurality of nodes to be deployed have completed configuring the installed database, and issues a database starting instruction to the plurality of nodes to be started if the determination result is yes.
And after the node to be started receives the database starting instruction, starting the database which is installed on the node and has completed configuration. And after all the nodes in the plurality of nodes to be started start the database, finishing the deployment of the distributed database.
The specific method and process for implementing the corresponding function by each module included in the distributed database deployment device are detailed in the embodiment of the distributed database deployment method, and are not described again here.
The distributed database deployment device is used for the distributed database deployment method in each of the foregoing embodiments. Therefore, the description and definition in the distributed database deployment method in the foregoing embodiments can be used for understanding the execution modules in the embodiments of the present invention.
The embodiment of the invention finishes the deployment of the distributed database through a unified platform, avoids the one-by-one deployment of the nodes, and particularly can greatly shorten the deployment time and greatly improve the deployment efficiency under the condition that the cluster comprises a large number of nodes. And by issuing the unified configuration file, the difference error caused by manually configuring the nodes one by one can be avoided, the error in the operation of the distributed database can be reduced, and the nodes can be started more conveniently.
Fig. 3 is a block diagram of an electronic device according to an embodiment of the present invention. Based on the content of the above embodiment, as shown in fig. 3, the electronic device may include: a processor (processor)301, a memory (memory)302, and a bus 303; the processor 301 and the memory 302 complete communication with each other through the bus 303; processor 301 is configured to invoke computer program instructions stored in memory 302 and executable on processor 301 to perform the distributed database deployment method provided by the above-described method embodiments, including, for example: acquiring an installation medium issuing instruction, and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction; if the installation medium is successfully issued to the plurality of nodes to be deployed, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and the database is installed on the node to be deployed; if the fact that the database is successfully installed on the multiple nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, the configuration file corresponding to the current deployment is issued to the multiple nodes to be deployed according to the configuration file issuing instruction, and each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment; and if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database according to the configuration file corresponding to the deployment, issuing a database starting instruction to the plurality of nodes to be started so that each node to be started starts the configured database.
Another embodiment of the present invention discloses a computer program product, the computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, which when executed by a computer, enable the computer to perform the distributed database deployment method provided by the above method embodiments, for example, including: acquiring an installation medium issuing instruction, and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction; if the installation medium is successfully issued to the plurality of nodes to be deployed, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and the database is installed on the node to be deployed; if the fact that the database is successfully installed on the multiple nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, the configuration file corresponding to the current deployment is issued to the multiple nodes to be deployed according to the configuration file issuing instruction, and each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment; and if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database according to the configuration file corresponding to the deployment, issuing a database starting instruction to the plurality of nodes to be started so that each node to be started starts the configured database.
Furthermore, the logic instructions in the memory 302 may be implemented in software functional units and stored in a computer readable storage medium when sold or used as a stand-alone product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods of the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Another embodiment of the present invention provides a non-transitory computer-readable storage medium, which stores computer instructions for causing a computer to execute the distributed database deployment method provided by the foregoing method embodiments, for example, the method includes: acquiring an installation medium issuing instruction, and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction; if the installation medium is successfully issued to the plurality of nodes to be deployed, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and the database is installed on the node to be deployed; if the fact that the database is successfully installed on the multiple nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, the configuration file corresponding to the current deployment is issued to the multiple nodes to be deployed according to the configuration file issuing instruction, and each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment; and if the plurality of nodes to be deployed are judged and known to complete the configuration of the installed database according to the configuration file corresponding to the deployment, issuing a database starting instruction to the plurality of nodes to be started so that each node to be started starts the configured database.
The above-described embodiments of the apparatus are merely illustrative, and units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment may be implemented by software plus a necessary general hardware platform, and may also be implemented by hardware. It is understood that the above-described technical solutions may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method of the above-described embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (7)
1. A distributed database deployment method, comprising:
acquiring an installation medium issuing instruction, and issuing an installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction;
if the installation medium is judged and known to be successfully issued to the plurality of nodes to be deployed, a decompression instruction is sent to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and a database is installed on the nodes to be deployed;
if the fact that the database is successfully installed on the plurality of nodes to be deployed is judged and known, a configuration file issuing instruction is obtained, a configuration file corresponding to the current deployment is issued to the plurality of nodes to be deployed according to the configuration file issuing instruction, and each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment;
if the fact that the plurality of nodes to be deployed complete the configuration of the installed database according to the configuration file corresponding to the deployment is judged, a database starting instruction is issued to the plurality of nodes to be started, so that each node to be started starts the configured database;
before the obtaining of the installation medium issuing instruction, the method further includes:
acquiring environment configuration of each node; the environment configuration of the node at least comprises: one of a port, an operating system version, a memory size, a CPU core number, a disk space size, and a network performance;
if the environment configuration of any node is judged and known to meet the deployment requirement of a database, determining the node as the node to be deployed;
after the database starting instruction is issued to a plurality of nodes to be started, the method further comprises the following steps:
acquiring a trigger stop instruction, and issuing a database stop instruction to a plurality of nodes to be stopped according to the trigger stop instruction so that each node to be stopped stops the operation of the database;
after the database starting instruction is issued to a plurality of nodes to be started, the method further comprises the following steps:
and acquiring the running state of each node, and if judging and knowing that the running state of any one node is abnormal, sending a restart instruction to the node so as to start the configured database after the node is restarted.
2. The method of claim 1, wherein before the obtaining the configuration file issuing instruction, further comprising:
acquiring a parameter configuration instruction, and generating a temporary configuration file according to the parameter configuration instruction;
and generating the configuration file corresponding to the deployment according to the temporary configuration file and the configuration file corresponding to the last deployment.
3. The method according to claim 2, wherein the specific step of generating the configuration file corresponding to the current deployment according to the temporary configuration file and the configuration file corresponding to the last deployment comprises:
for any parameter in the temporary configuration file, configuring the value of the parameter in the configuration file corresponding to the deployment at this time as the value of the parameter in the temporary configuration file;
and for any parameter in the configuration file corresponding to the last deployment, if the parameter does not exist in the temporary configuration file, configuring the value of the parameter in the configuration file corresponding to the current deployment as the value of the parameter in the configuration file corresponding to the last deployment.
4. The method of claim 1, wherein after issuing the database startup instruction to a plurality of nodes to be started, further comprising:
and monitoring the running state of the database deployed by each node, and sending an alarm if judging that the running state of the database deployed by any one node is abnormal.
5. A distributed database deployment apparatus, comprising:
the installation source issuing module is used for acquiring an installation medium issuing instruction and issuing the installation medium to a plurality of nodes to be deployed according to the installation medium issuing instruction;
the installation source decompression module is used for sending a decompression instruction to the plurality of nodes to be deployed if the installation medium is judged and known to be successfully issued to the plurality of nodes to be deployed, so that each node to be deployed decompresses the installation medium according to the decompression instruction, and a database is installed on the nodes to be deployed;
the database configuration module is used for acquiring a configuration file issuing instruction if the database is judged to be successfully installed on the plurality of nodes to be deployed, and issuing the configuration file corresponding to the current deployment to the plurality of nodes to be deployed according to the configuration file issuing instruction so that each node to be deployed configures the installed database according to the configuration file corresponding to the current deployment;
the database starting module is used for issuing a database starting instruction to the plurality of nodes to be started if the plurality of nodes to be deployed are judged to complete the configuration of the installed database according to the configuration file corresponding to the deployment, so that each node to be started starts the configured database;
the installation source issuing module is also used for acquiring the environment configuration of each node; the environment configuration of the node at least comprises: one of a port, an operating system version, a memory size, a CPU core count, a disk space size, and a network performance; if the environment configuration of any node is judged and known to meet the deployment requirement of a database, determining the node as the node to be deployed;
the database starting module is further used for acquiring a trigger stopping instruction, and issuing the database stopping instruction to a plurality of nodes to be stopped according to the trigger stopping instruction so that each node to be stopped stops the operation of the database;
the database starting module is further configured to obtain the operating state of each node, and if the operating state of any one of the nodes is judged to be abnormal, send a restart instruction to the node, so that the configured database is started after the node is restarted.
6. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the distributed database deployment method according to any one of claims 1 to 4 are implemented when the program is executed by the processor.
7. A non-transitory computer readable storage medium, having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the distributed database deployment method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910236419.XA CN110007934B (en) | 2019-03-27 | 2019-03-27 | Distributed database deployment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910236419.XA CN110007934B (en) | 2019-03-27 | 2019-03-27 | Distributed database deployment method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110007934A CN110007934A (en) | 2019-07-12 |
| CN110007934B true CN110007934B (en) | 2022-09-13 |
Family
ID=67168405
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910236419.XA Active CN110007934B (en) | 2019-03-27 | 2019-03-27 | Distributed database deployment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110007934B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111581014B (en) * | 2020-03-30 | 2024-03-22 | 中国建设银行股份有限公司 | Method and device for restarting automatic control host and related equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224348A (en) * | 2014-06-11 | 2016-01-06 | 中兴通讯股份有限公司 | A kind of installation method of MySQL database and device |
| CN107515766A (en) * | 2017-08-24 | 2017-12-26 | 北京锐安科技有限公司 | Generation method, deployment installation method and the device of database deployment file |
| CN107544830A (en) * | 2017-09-21 | 2018-01-05 | 郑州云海信息技术有限公司 | A kind of method and device of automatic installation database |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9641388B2 (en) * | 2014-07-29 | 2017-05-02 | Commvault Systems, Inc. | Customized deployment in information management systems |
-
2019
- 2019-03-27 CN CN201910236419.XA patent/CN110007934B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224348A (en) * | 2014-06-11 | 2016-01-06 | 中兴通讯股份有限公司 | A kind of installation method of MySQL database and device |
| CN107515766A (en) * | 2017-08-24 | 2017-12-26 | 北京锐安科技有限公司 | Generation method, deployment installation method and the device of database deployment file |
| CN107544830A (en) * | 2017-09-21 | 2018-01-05 | 郑州云海信息技术有限公司 | A kind of method and device of automatic installation database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110007934A (en) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11914486B2 (en) | Cloning and recovery of data volumes | |
| CN108234170B (en) | Monitoring method and device for server cluster | |
| US8321549B2 (en) | Action execution management for service configuration items | |
| CN107844343B (en) | Upgrading system and method for complex server application system | |
| CN111416821A (en) | Internet of things equipment information acquisition method, system and device | |
| CN103699489A (en) | Software remote fault diagnosis and repair method based on knowledge base | |
| JP2016514299A (en) | Parallel execution of continuous event processing (CEP) queries | |
| EP3591485B1 (en) | Method and device for monitoring for equipment failure | |
| CN111125444A (en) | Big data task scheduling management method, device, equipment and storage medium | |
| WO2022036901A1 (en) | Implementation method and apparatus for redis replica set | |
| CN110895488B (en) | Task scheduling method and device | |
| WO2014203262A1 (en) | Monitoring a computing network | |
| CN106657167A (en) | Management server, server cluster and management method | |
| US10664335B2 (en) | System and method for maintaining the health of a machine | |
| CN110063042A (en) | A kind of response method and its terminal of database failure | |
| CN113778486A (en) | Containerization processing method, device, medium and equipment for code pipeline | |
| CN117130730A (en) | Metadata management method for federal Kubernetes cluster | |
| CN110007934B (en) | Distributed database deployment method and device | |
| CN110275793B (en) | Detection method and equipment for MongoDB data fragment cluster | |
| CN115314361B (en) | Server cluster management method and related components thereof | |
| CN114640709B (en) | Edge node processing method, device and medium | |
| CN116069358A (en) | Method, device and storage medium for upgrading data in distributed database | |
| CN112765188B (en) | Configuration information processing method, configuration management system, electronic device and storage medium | |
| CN115114284A (en) | Table change processing method and system | |
| CN114500106A (en) | Security management method, device, equipment and storage medium for server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |