WO2020224238A1

WO2020224238A1 - Blockchain node depolyment method, device and equipment, and storage medium

Info

Publication number: WO2020224238A1
Application number: PCT/CN2019/120650
Authority: WO
Inventors: 褚镇飞; 张伟
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2019-05-06
Filing date: 2019-11-25
Publication date: 2020-11-12
Also published as: CN110224854B; CN110224854A

Abstract

The present application relates to blockchain technology, and provides a blockchain node deployment method, device, and equipment, and a storage medium. The method comprises: obtaining a configuration file of each blockchain node, wherein the blockchain nodes comprise consensus nodes, data nodes, and client nodes; sequentially deploying and starting the consensus nodes, the data nodes, and the client nodes according to the configuration file; in the process of deploying and starting the consensus nodes, the data nodes and the client nodes, when a preset type of error information appears in the log of the blockchain nodes, pausing the deployment and starting of the consensus nodes, the data nodes or the client nodes, deleting the configuration file and all processes of the blockchain nodes corresponding to the error information, and deploying and starting the corresponding blockchain nodes again. The present application can reduce the deployment difficulty of blockchain nodes, and improve the deployment efficiency of blockchain nodes.

Description

Deployment method, device, equipment and storage medium of blockchain node

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910371483.9, and the invention title is "Blockchain node deployment method, device and storage medium" on May 6, 2019, the entire content of which is by reference Incorporate in the application.

Technical field

This application relates to the field of blockchain technology, and in particular to a method, device, equipment and computer-readable storage medium for deploying blockchain nodes.

Background technique

Blockchain is generally understood as a distributed ledger, which is essentially a distributed computing and storage system. The inventor realizes that because the blockchain system often has many nodes and each node may be distributed across regions, the deployment of blockchain nodes, especially the deployment of alliance chain system nodes, is often very cumbersome. Once the wrong node is found, it may be necessary Redeploy a large number of related nodes.

Summary of the invention

In view of the above reasons, it is necessary to provide a blockchain node deployment method, device, equipment, and computer-readable storage medium to reduce the difficulty of blockchain node deployment, improve the deployment efficiency of blockchain nodes, and find deployment errors. When blockchain nodes are used, there is no need to redeploy other blockchain nodes.

In order to achieve the above objective, the first aspect of the present application provides a method for deploying blockchain nodes. The method includes: a configuration file obtaining step: obtaining a configuration file of each blockchain node, wherein the blockchain node Including consensus nodes, data nodes and client nodes; consensus node deployment steps: deploy and start the consensus nodes according to the configuration files of each consensus node; data node deployment steps: after all the consensus nodes are successfully deployed, according to each data node The configuration file for deploying and starting the data node; and the client node deployment step: after all the data nodes are successfully deployed, deploy and start the client node according to the configuration file of each client node.

The second aspect of the application provides a device for deploying blockchain nodes, including: a configuration module for obtaining configuration files of each blockchain node, where the blockchain nodes include consensus nodes, data nodes, and Client node; deployment module, including: consensus node deployment unit, used to deploy and start the consensus node according to the configuration file of each consensus node; data node deployment unit, used to deploy all the consensus nodes according to each The configuration file of the data node deploys and starts the data node; and the client node deployment unit is configured to deploy and start the client node according to the configuration file of each client node after all the data nodes are successfully deployed.

A third aspect of the present application provides a device for deploying blockchain nodes, including: a memory and at least one processor, the memory stores instructions, and the memory and the at least one processor are interconnected by wires; At least one processor calls the instructions in the memory, so that the deployment device of the blockchain node executes the method described in the first aspect.

The fourth aspect of the present application provides a computer-readable storage medium, the computer-readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer executes the above-mentioned first aspect method.

The deployment method, device, equipment, and computer-readable storage medium of blockchain nodes provided in this application obtain the configuration file of each blockchain node, and then deploy and start the blockchain consensus node in turn according to the configuration file. Blockchain data nodes and blockchain client nodes, and in the process of deploying and starting the blockchain consensus nodes, data nodes, and client nodes, use the logs of the blockchain nodes to monitor the process, when When a preset type of error message appears in the log, suspend the deployment and startup of the consensus node, data node or client node, delete the configuration file and all processes of the blockchain node corresponding to the error message, and redeploy And start the corresponding blockchain node, and then continue to execute the deployment and start of the consensus node, data node or client node. Because the blockchain nodes are deployed and started in the order of consensus node, data node, and client node, when the data node is deployed, the consensus node has been successfully deployed and started, so when the data node is deployed incorrectly, no It will affect the consensus node. Similarly, when the client node is deployed incorrectly, it will not affect the consensus node and the data node. Because the configuration file of each blockchain node exists independently, when a blockchain node is deployed incorrectly, other nodes will not be affected. In summary, using this application can reduce the difficulty of deploying blockchain nodes, and there is no need to redeploy other nodes when a wrong node is discovered. Because the same type of blockchain nodes can be deployed concurrently, this application can also improve the deployment efficiency of blockchain nodes.

Description of the drawings

Fig. 1 is a schematic diagram of an embodiment of an electronic device of this application;

FIG. 2 is a program module diagram of an embodiment of the deployment program of blockchain nodes in FIG. 1;

FIG. 3 is a flowchart of an embodiment of a method for deploying a blockchain node of this application;

FIG. 4 is a detailed flowchart of step S310 in FIG. 3.

Detailed ways

This application provides a method, device, device, and computer-readable storage medium for deploying blockchain nodes, which reduces the difficulty of deployment of blockchain nodes, improves the deployment efficiency of blockchain nodes, and finds deployment errors in blockchains. There is no need to redeploy other blockchain nodes.

In order to enable those skilled in the art to better understand the solutions of the present application, the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, without having to use To describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order other than the content illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device including a series of steps or units is not necessarily limited to those clearly listed Steps or units, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

For ease of understanding, the following describes the specific process of the embodiment of the present application, please refer to FIG. 1, which is a schematic diagram of the electronic device 1 in the embodiment of the present application. In this embodiment, the electronic device 1 can be connected to a blockchain node (not shown in the figure) through a network. The electronic device 1 can be a server, a smart phone, a tablet computer, a portable computer, a desktop computer, etc. Terminal equipment with storage and computing functions. In an embodiment, when the electronic device 1 is a server, the server may be one or more of a rack server, a blade server, a tower server, or a cabinet server.

The electronic device 1 includes a memory 11, a processor 12 and a network interface 13.

Wherein, the memory 11 includes at least one type of readable storage medium. The at least one type of readable storage medium may be a non-volatile storage medium such as flash memory, hard disk, multimedia card, card-type memory, and the like. In some embodiments, the readable storage medium may be an internal storage unit of the electronic device 1, such as a hard disk of the electronic device 1. In other embodiments, the readable storage medium may also be an external memory of the electronic device 1, such as a plug-in hard disk or a smart memory card (Smart Media Card, SMC) equipped on the electronic device 1. Secure Digital (SD) card, flash card (Flash Card), etc.

In this embodiment, the readable storage medium of the memory 11 is used to store the deployment program 10 of the blockchain node and the data generated during the deployment of the blockchain node, such as the configuration information of each blockchain node, The corresponding relationship between the configuration information and the blockchain node identification, etc. The memory 11 can also be used to temporarily store data that has been output or will be output.

The processor 12 may be a central processing unit (CPU), a microprocessor or other data processing chip, and is used to run the program code or process data stored in the memory 11, for example to execute the deployment of the blockchain node Procedure 10.

The network interface 13 may include a standard wired interface and a wireless interface (such as a Wi-Fi interface). It is usually used to establish a communication connection between the electronic device 1 and other electronic devices, such as establishing a communication connection with a certificate authority (CA) and consensus nodes, data nodes, and client nodes of the blockchain.

FIG. 1 only shows the electronic device 1 with the components 11-13, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.

Optionally, the electronic device 1 may also include an input unit such as a keyboard (Keyboard), a voice input device such as a microphone (Microphone) and other devices with a voice recognition function. The input unit and the input device can be used to edit, add and delete the deployment program 10 of the blockchain node.

Optionally, the electronic device 1 may also include a display, which may also be called a display screen or a display unit. In some embodiments, it may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an organic light-emitting diode (OLED) display, etc. The display is used for displaying information processed in the electronic device 1 and for displaying a visualized user interface.

The electronic device 1 may also include a radio frequency (RF) circuit, a sensor, an audio circuit, a wired interface, a wireless interface, and so on, which will not be repeated here.

In the above embodiment, the blockchain nodes include consensus nodes, data nodes, and client nodes. It is assumed that the software environment of all blockchain nodes has been installed using existing technology, that is, the operating system and The application software has been installed, and the processor 12 may implement the following steps when executing the deployment program 10 of the blockchain node stored in the memory 11:

Configuration file obtaining step: obtaining configuration files of each blockchain node, where the blockchain nodes include consensus nodes, data nodes, and client nodes;

Consensus node deployment steps: deploy and start the consensus node according to the configuration file of each consensus node;

Data node deployment steps: after all the consensus nodes are successfully deployed, deploy and start the data nodes according to the configuration files of each data node; and

Client node deployment steps: After all the data nodes are successfully deployed, deploy and start the client nodes according to the configuration files of each client node.

For a detailed description of the above steps, please refer to the following description of the program module diagram of the embodiment 10 of the deployment program of blockchain nodes in FIG. 2 and the description of the flowcharts of the embodiment of the deployment method of blockchain nodes in FIG. 3 and FIG. 4.

In other embodiments, the deployment program 10 of the blockchain node may be divided into multiple modules, and the multiple modules are stored in the memory 12 and executed by the processor 13 to complete the application. The module referred to in this application refers to a series of computer program instruction segments that can complete specific functions.

Referring to FIG. 2, it is a program module diagram of an embodiment of the deployment program 10 of blockchain nodes in FIG. 1. In this embodiment, the deployment program 10 of the blockchain node can be divided into: a configuration module 110, a deployment module 120, a monitoring module 130, and a deletion module 140.

The configuration module 110 is configured to assign a unique node identifier to each blockchain node, obtain configuration information corresponding to the node identifier, and write the configuration information into the configuration of each blockchain node File. Wherein, the blockchain nodes include consensus nodes, data nodes and client nodes. The client node is used to send a request to the data node, the data node is used to receive the request sent by the client and endorses the request and simulates the execution of the request, and the consensus node is used to execute the request The result is processed by consensus and blocks are generated. The configuration information includes node identity information, node IP address and node port information. In this embodiment, the node identity information includes a digital certificate issued by a predetermined CA for the blockchain node to prove the legal identity of the blockchain node. The node identifier may use the node IP address of the corresponding blockchain node or other identifiers that can uniquely identify the blockchain node, and the format of the configuration file may be XML or JSON, which is not limited in this application.

The deployment module 120 is configured to sequentially deploy and start the blockchain consensus node, the blockchain data node, and the blockchain client node according to the configuration file. In this embodiment, the deployment module 120 includes a consensus node deployment unit 121, a data node deployment unit 122, and a client node deployment module 123. The consensus node deployment unit 121 is configured to deploy and start the consensus node according to the configuration file of each consensus node, and the data node deployment unit 122 is configured to, after all the consensus nodes are successfully deployed, according to the configuration file of each data node The data node is deployed and started, and the client node deployment module 123 is configured to deploy and start the client node according to the configuration file of each client node after all the data nodes are successfully deployed.

In this embodiment, the deployment and startup of the consensus node, data node, and client node can be performed concurrently, respectively, so as to improve the deployment efficiency of blockchain nodes, especially the deployment efficiency of data nodes and client nodes, because Blockchain systems usually include a large number of data nodes and client nodes. Specifically, the concurrent deployment threshold can be set through the deployment module 120, so as to limit the maximum number of concurrent deployments and startups of the same type of blockchain nodes. The setting of the concurrent deployment threshold is affected by the performance of the electronic device 1. How many processes the electronic device 1 can create for the deployment and startup of blockchain nodes can set the concurrent deployment threshold. For example, assuming that the electronic device 1 can create 1000 processes for deploying and starting a blockchain node, and each process is responsible for deploying and starting a blockchain node, the concurrent deployment threshold can be set to 1000. By concurrently deploying the same type of blockchain nodes, the deployment efficiency of blockchain nodes can be greatly improved.

The monitoring module 130 is used to monitor the deployment and startup of the consensus node, data node and client node. In this embodiment, the log of the blockchain node is used to monitor the deployment and startup of the consensus node, data node, and client node. For example, an alarm keyword (such as "error") can be set to monitor a preset type of Error information, such as startup failure, abnormal operation, etc. When deploying and starting the blockchain node, if the alarm keyword appears in the log of the blockchain node, it means that an abnormal state has occurred during the deployment and startup process, and the area with the abnormal state needs to be redeployed Block chain node.

The deletion module 140 is used to suspend the deployment and startup of the consensus node, data node, and client node when the monitoring module 130 finds an abnormal state, and delete the configuration file of the blockchain node corresponding to the abnormal state With all processes (including containers and mirrors), the blockchain node is handed over to the configuration module 110 and the deployment module 120, the configuration file is retrieved and loaded, and the deployment and startup are performed again.

In addition, this application also provides a method for deploying blockchain nodes. Referring to FIG. 3, it is a flowchart of an embodiment of a method for deploying a blockchain node in this application. The processor 12 of the electronic device 1 implements the following steps of the blockchain node deployment method when executing the blockchain node deployment program 10 stored in the memory 11:

In step S300, the configuration module 110 is used to obtain the configuration file of each blockchain node. Wherein, the blockchain nodes include consensus nodes, data nodes, and client nodes, and the configuration file includes configuration information of each blockchain node, such as node identity information, node IP address, and node port information.

Specifically, each blockchain node has a unique node identifier, and the node identifier of each blockchain has a predetermined corresponding relationship with its configuration information. The node identifier can use the node IP address or other uniquely identifying blocks. The identifier of the chain node, the configuration information can be obtained from a predetermined configuration center. For example, the configuration center may obtain a digital certificate representing the node identity information of each blockchain node from at least one predetermined CA. The CA used by different blockchain nodes to obtain the node identity information may be the same or different. The configuration center may specify the CA that issues the digital certificate according to the node identifier or the node type. The configuration center can also obtain the node IP address of each blockchain node through the command "ifconfig|grep broadcast|awk'{print$2}'". The node port information can be pre-appointed or through similar Method to obtain, I will not repeat it here. After the configuration module 110 obtains the configuration information corresponding to each node identifier, it writes the configuration information into the configuration file of each blockchain node for the deployment module 120 to use.

In step S310, the deployment module 120 sequentially deploys and starts the consensus node, the data node and the client node according to the configuration file. Specifically, the deployment module 120 should first complete the concurrent deployment and startup of the consensus node, then complete the concurrent deployment and startup of the data node, and finally concurrently deploy and start the client node. Assuming that all the consensus nodes are successfully deployed and started, and no abnormal state occurs, it means that all the consensus nodes are successfully deployed, and the deployment and startup of the data nodes will begin. When the data node is started, each data node will establish a connection with the consensus node. If the connection is successfully established and is operating normally, the data node is successfully deployed. If the connection is not established or the operation is abnormal, the data node If there is an abnormality, it is necessary to eliminate the abnormality of the data node and redeploy and start the data node. Similarly, assuming that all consensus nodes and all data nodes are successfully deployed and started, and no abnormal state occurs, it means that all consensus nodes and all data nodes are successfully deployed, and the deployment and startup of the client nodes will begin. When starting the client node, each client node will establish a connection with at least one of the data nodes. If the connection is successfully established and is operating normally, the deployment of the client node is successful. If the connection is not established or the operation is abnormal , Indicating that there is an abnormality in the client node, it is necessary to eliminate the abnormality of the client node and redeploy and start the client node.

In other embodiments, the configuration information of the blockchain node may also include a time threshold for requesting to establish a connection, when the connection between the corresponding blockchain nodes cannot be successfully established within the time threshold.

Deploy the blockchain nodes in the order of consensus nodes, data nodes, and client nodes to ensure that nodes deployed later will not affect the nodes deployed earlier. When an abnormal blockchain node is found , Just eliminate the abnormal state of the blockchain node, redeploy and start the blockchain node, without redeploying other blockchain nodes.

In this embodiment, the concurrent deployment threshold is set to limit the number of concurrent deployment of the same type of blockchain nodes. Each process created by the electronic device 1 can be responsible for deploying and starting a blockchain node. By concurrently deploying the same type of blockchain nodes, the deployment efficiency of blockchain nodes can be greatly improved.

Step S320: Use the monitoring module 130 to monitor the deployment and startup of the consensus nodes, data nodes, and client nodes. When an abnormal state is found, suspend the deployment and startup of subsequent blockchain nodes in step S310 (without interrupting the deployment being deployed And the activated blockchain node), using the deletion module 140 to delete the configuration file and all processes of the blockchain node corresponding to the abnormal state, redeploy and start the blockchain node, and deploy on the blockchain node After success, proceed to step S310. Specifically, the log of the blockchain node can be used to monitor the deployment and startup of the blockchain node. By setting an alarm keyword (such as "error"), when the alarm keyword appears in the log, the consensus is automatically suspended The deployment and startup of nodes, data nodes or client nodes, locate the abnormal blockchain node according to the blockchain node of the log where the alarm keyword appears, and determine the block based on the row information of the alarm keyword The abnormal state of the chain node is then excluded. For example, the abnormal state can be eliminated by deleting the configuration file and all processes (including containers and mirrors) of the blockchain node, and then redeploying and starting the blockchain node. After it is determined that the blockchain node is successfully deployed, the step S310 is continued.

Referring to FIG. 4, a detailed flowchart of step S310 of the deployment method of a blockchain node of this application is shown, and the step S310 includes the following steps:

In step S311, the consensus node deployment unit 121 deploys and starts the consensus node according to the configuration file of each consensus node. Because the number of consensus nodes is often small, the electronic device 1 can create the same process as the number of consensus nodes that need to be deployed and started to be responsible for the deployment and start of the consensus node, and each process is responsible for deploying and starting a consensus node . After it is determined that all the consensus nodes are successfully deployed, step S312 is executed.

In step S312, the data node deployment unit 122 deploys and starts the data node according to the configuration file of each data node. Because the number of data nodes is often large, the electronic device 1 can create processes according to the number of data nodes or create processes in batches that are not greater than the concurrent deployment threshold to be responsible for the deployment and startup of the data nodes, and each process is responsible for Deploy and start a data node. After it is determined that all the data nodes are successfully deployed, step S313 is executed.

In step S312, the client node deployment unit 123 deploys and starts the client node according to the configuration file of each client node. Because the number of client nodes is often large, the electronic device 1 can create processes in which the number of processes is not greater than the concurrent deployment threshold according to the number of client nodes to be responsible for the deployment and startup of the client nodes, and each process is responsible for Deploy and start a client node.

It can be judged whether the consensus node, data node, and client node are successfully deployed according to the log of the blockchain node. For details, please refer to the relevant introduction of FIG. 3 above, which will not be repeated here.

In addition, the present application also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on the computer, the computer executes the following steps:

The specific implementation is roughly the same as the deployment method of the blockchain node and the specific implementation of the electronic device 1. Please refer to the schematic diagram of the embodiment of the electronic device 1 in Figure 1 and Figure 3 and Figure 4 on the deployment of the blockchain node. The detailed introduction of the flowchart of the method embodiment will not be repeated here.

It should be noted that in this article, the terms "including", "including" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, device, article, or method. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on what can be achieved by a person of ordinary skill in the art. When the combination of technical solutions is contradictory or cannot be achieved, it should be considered that such a combination of technical solutions does not exist. , Not within the scope of protection required by this application.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of the present application essentially or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium as described above and includes several instructions. It is used to make the electronic device execute the method described in each embodiment of the present application.

The above are only preferred embodiments of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly used in other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A method for deploying blockchain nodes, the method for deploying blockchain nodes includes:

Configuration file obtaining step: obtaining configuration files of each blockchain node, where the blockchain nodes include consensus nodes, data nodes, and client nodes;

Consensus node deployment steps: deploy and start the consensus node according to the configuration file of each consensus node;

Data node deployment steps: after all the consensus nodes are successfully deployed, deploy and start the data nodes according to the configuration files of each data node; and

Client node deployment steps: After all the data nodes are successfully deployed, deploy and start the client nodes according to the configuration files of each client node.
The method for deploying blockchain nodes according to claim 1, wherein the configuration file obtaining step comprises:

Allocating a unique node identifier for each blockchain node;

Obtaining configuration information corresponding to the node identifier, the configuration information including node identity information, node IP address, and node port information; and

The configuration information is written into the configuration file of each blockchain node.
The method for deploying blockchain nodes according to claim 1 or 2, the method further comprising:

Use the logs of blockchain nodes to monitor the deployment and startup of the consensus nodes, data nodes and client nodes;

When a preset type of error message appears in the log, suspend the deployment and startup of the consensus node, data node or client node, delete the configuration file and all processes of the blockchain node corresponding to the error message, and restart Deploy and start the corresponding blockchain node.
The method for deploying blockchain nodes according to claim 3, the method for deploying blockchain nodes further comprises:

The deployment and startup of the same type of blockchain nodes are performed concurrently.
The method for deploying blockchain nodes according to claim 4, the method for deploying blockchain nodes further comprises:

Limit the maximum number of concurrent deployments and startups of the same type of blockchain nodes by setting the concurrent deployment threshold.
A deployment device for blockchain nodes, the deployment device for blockchain nodes includes:

The configuration module is used to obtain the configuration file of each block chain node, where the block chain node includes a consensus node, a data node and a client node;

Deployment modules, including:

The consensus node deployment unit is used to deploy and start the consensus node according to the configuration file of each consensus node;

The data node deployment unit is used to deploy and start the data node according to the configuration file of each data node after all the consensus nodes are successfully deployed; and

The client node deployment unit is configured to deploy and start the client node according to the configuration file of each client node after all the data nodes are successfully deployed.
The device for deploying blockchain nodes according to claim 6, wherein the configuration module is specifically configured to:

Allocating a unique node identifier for each blockchain node;

Obtaining configuration information corresponding to the node identifier, the configuration information including node identity information, node IP address, and node port information; and

The configuration information is written into the configuration file of each blockchain node.
The deployment device for blockchain nodes according to claim 6 or 7, the deployment device for blockchain nodes further comprising:

The monitoring module is used to monitor the deployment and startup of the consensus node, data node and client node by using the log of the blockchain node;

The delete module is used to suspend the deployment and startup of the consensus node, data node or client node when a preset type of error message appears in the log, and delete the configuration file of the blockchain node corresponding to the error message With all processes, redeploy and start the corresponding blockchain node.
According to the deployment device of a blockchain node according to claim 8, the deployment module is specifically configured to:

The deployment and startup of the same type of blockchain nodes are performed concurrently.
According to the deployment device of a blockchain node according to claim 9, the deployment module is further specifically configured to:

Limit the maximum number of concurrent deployments and startups of the same type of blockchain nodes by setting the concurrent deployment threshold.
A deployment device for a blockchain node includes a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the processor implements the following steps when the processor executes the computer program:

Configuration file obtaining step: obtaining configuration files of each blockchain node, where the blockchain nodes include consensus nodes, data nodes, and client nodes;

Consensus node deployment steps: deploy and start the consensus node according to the configuration file of each consensus node;

Data node deployment steps: after all the consensus nodes are successfully deployed, deploy and start the data nodes according to the configuration files of each data node; and

Client node deployment steps: After all the data nodes are successfully deployed, deploy and start the client nodes according to the configuration files of each client node.
The deployment device of a blockchain node according to claim 11, when the processor executes the computer program to implement the configuration file obtaining step, it comprises the following steps:

Allocating a unique node identifier for each blockchain node;

Obtaining configuration information corresponding to the node identifier, the configuration information including node identity information, node IP address, and node port information; and

The configuration information is written into the configuration file of each blockchain node.
The deployment device of a blockchain node according to claim 11 or 12, when the processor executes the computer program to implement the deployment method of the blockchain node, the method includes the following steps:

Use the logs of blockchain nodes to monitor the deployment and startup of the consensus nodes, data nodes and client nodes;

When a preset type of error message appears in the log, suspend the deployment and startup of the consensus node, data node or client node, delete the configuration file and all processes of the blockchain node corresponding to the error message, and restart Deploy and start the corresponding blockchain node.
The deployment device of a blockchain node according to claim 13, when the processor executes the computer program to implement the deployment method of the blockchain node, the method includes the following steps:

The deployment and startup of the same type of blockchain nodes are performed concurrently.
The deployment device of a blockchain node according to claim 14, when the processor executes the computer program to implement the deployment method of the blockchain node, the method includes the following steps:

Limit the maximum number of concurrent deployments and startups of the same type of blockchain nodes by setting the concurrent deployment threshold.
A computer-readable storage medium that stores computer instructions, and when the computer instructions are executed on a computer, the computer executes the following steps:

Configuration file obtaining step: obtaining configuration files of each blockchain node, where the blockchain nodes include consensus nodes, data nodes, and client nodes;

Consensus node deployment steps: deploy and start the consensus node according to the configuration file of each consensus node;

Data node deployment steps: after all the consensus nodes are successfully deployed, deploy and start the data nodes according to the configuration files of each data node; and

Client node deployment steps: After all the data nodes are successfully deployed, deploy and start the client nodes according to the configuration files of each client node.
16. The computer-readable storage medium according to claim 16, when the computer instruction executes the configuration file obtaining step on the computer, the computer executes the following steps:

Allocating a unique node identifier for each blockchain node;

Obtaining configuration information corresponding to the node identifier, the configuration information including node identity information, node IP address, and node port information; and

The configuration information is written into the configuration file of each blockchain node.
The computer-readable storage medium according to claim 16 or 17, when the computer instructions run the steps of the blockchain node deployment method on the computer, the computer is caused to execute the following steps:

Use the logs of blockchain nodes to monitor the deployment and startup of the consensus nodes, data nodes and client nodes;

When a preset type of error message appears in the log, suspend the deployment and startup of the consensus node, data node or client node, delete the configuration file and all processes of the blockchain node corresponding to the error message, and restart Deploy and start the corresponding blockchain node.
The computer-readable storage medium according to claim 18, when the computer instructions run the steps of the blockchain node deployment method on the computer, the computer is caused to perform the following steps:

The deployment and startup of the same type of blockchain nodes are performed concurrently.
The computer-readable storage medium according to claim 19, when the computer instructions run the steps of the blockchain node deployment method on the computer, the computer is caused to perform the following steps:

Limit the maximum number of concurrent deployments and startups of the same type of blockchain nodes by setting the concurrent deployment threshold.