WO2020224236A1 - 区块链数据处理的装置、方法、系统及存储介质 - Google Patents
区块链数据处理的装置、方法、系统及存储介质 Download PDFInfo
- Publication number
- WO2020224236A1 WO2020224236A1 PCT/CN2019/120589 CN2019120589W WO2020224236A1 WO 2020224236 A1 WO2020224236 A1 WO 2020224236A1 CN 2019120589 W CN2019120589 W CN 2019120589W WO 2020224236 A1 WO2020224236 A1 WO 2020224236A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- chain
- data
- predetermined
- chain data
- Prior art date
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
-
- 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
Definitions
- This application relates to the field of blockchain technology, and in particular to a device, method, system and storage medium for blockchain data processing.
- Blockchain is generally understood as a distributed ledger, and its essence is also a distributed database.
- a blockchain node In the consortium chain scenario, due to the introduction of multiple chains, a blockchain node often belongs to multiple blockchains at the same time.
- the device where the blockchain node is located stores data from multiple chains, the block data will be stored and differentiated, but other data will be combined and stored, which is relatively simple to implement.
- a new node needs to be created. The new node starts to synchronize data from the genesis block (ie the first block) in order to synchronize data on the same chain to On the newly created node.
- the inventor realized that this method of data processing is cumbersome and low in efficiency, which increases network pressure on other nodes and wastes system resources.
- the purpose of this application is to provide a block chain data processing device, method, system and storage medium, aiming to realize simple and efficient expansion operations in a multi-chain scenario.
- the device for processing blockchain data includes a memory and a processor connected to the memory.
- the processing system is executed by the processor, the following steps are implemented:
- the monitoring smart contract is called to monitor the system information of the node, and the system information includes the storage capacity of the node;
- the multi-chain data stored on the node is planned according to the chain name, and the multi-chain data with the same chain name is divided into the same pre-created directory in;
- the multi-chain data is deleted.
- the multi-chain data includes block data, index data, status data and historical data.
- system information further includes data status information of multi-chain data, and when the processing system is executed by the processor, the following steps are further implemented:
- the invalid Multi-chain data is planned according to the chain name, and invalid multi-chain data with the same chain name is divided into the same pre-created directory;
- the invalid multi-chain data is deleted.
- the current storage capacity of the node is sent to a predetermined terminal for display and warning.
- this application also provides a method for processing blockchain data, and the method for processing blockchain data includes:
- the monitoring smart contract is called to monitor the system information of the node, and the system information includes the storage capacity of the node;
- the multi-chain data includes block data, index data, status data and historical data.
- the system information further includes data status information of the multi-link data, and after the step S1, it further includes:
- the invalid Multi-chain data is planned according to the chain name, and invalid multi-chain data with the same chain name is divided into the same pre-created directory;
- the invalid multi-chain data is deleted.
- the method further includes: if it is monitored that the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, sending the current storage capacity of the node to a predetermined terminal for display and warning.
- the method further includes: obtaining smart contract information from the configuration file of the node, and if the smart contract information does not include the monitoring smart contract, installing the monitoring smart contract.
- the present application also provides a computer-readable storage medium on which a processing system is stored, and when the processing system is executed by a processor, the steps of the above-mentioned blockchain data processing method are realized.
- this application monitors the storage capacity of the node by invoking the monitoring smart contract. If the storage capacity of a node reaches the bottleneck, the storage situation of the data node will be transformed, and the multi-chain data stored on the node will be The chain name is planned, and the multi-chain data of the same chain name is divided into the same pre-created directory, and the data is stored according to the chain. After the new node is started, the directory is synchronized to the new node. The new node By searching and reading the data corresponding to the chain name in the directory to this node, the application of the capacity expansion scenario is completed, so that the data of part of the chain can be moved to the new node to achieve expansion. This method is simple and efficient to operate. There is no need to synchronize data block by block, which reduces network pressure on other nodes and saves system resources.
- FIG. 1 is a schematic diagram of the hardware architecture of an embodiment of a device for processing blockchain data in this application;
- FIG. 2 is a program module diagram of an embodiment of the processing system in FIG. 1;
- FIG. 3 is a schematic flowchart of an embodiment of a method for processing blockchain data in this application.
- the block chain data processing device 1 is a device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions.
- the block chain data processing device 1 may be a computer, a single network server, a server group composed of multiple network servers, or a cloud composed of a large number of hosts or network servers based on cloud computing, where cloud computing is distributed A type of computing, a super virtual computer composed of a group of loosely coupled computer sets.
- the block chain data processing device 1 may include, but is not limited to, a memory 11, a processor 12, and a network interface 13 that can be communicated with each other through a system bus.
- the memory 11 is stored on the processor 12 Operating processing system 10. It should be pointed out that Figure 1 only shows the device 1 for blockchain data processing with components 11-13, but it should be understood that it is not required to implement all the components shown, and more or more can be implemented instead. Few components.
- the memory 11 includes a memory and at least one type of readable storage medium.
- the memory provides cache for the operation of the device 1 for blockchain data processing;
- the readable storage medium can be, for example, flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static Non-volatile storage media such as random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disks, optical disks, etc. .
- the readable storage medium may be an internal storage unit of the device 1 for blockchain data processing, such as the hard disk of the device 1 for blockchain data processing; in other embodiments, the non-volatile The storage medium can also be an external storage device of the device 1 for blockchain data processing, such as a plug-in hard disk equipped on the device 1 for blockchain data processing, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital). Digital, SD) card, flash card (Flash Card), etc.
- the readable storage medium of the memory 11 is generally used to store the operating system and various application software installed in the blockchain data processing device 1, for example, to store the program code of the processing system 10 in an embodiment of the present application Wait.
- the memory 11 can also be used to temporarily store various types of data that have been output or will be output.
- the processor 12 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments, and is used to run data stored in the memory 11 Program code or processing data, such as running the processing system 10, etc.
- CPU Central Processing Unit
- controller microcontroller
- microprocessor or other data processing chip in some embodiments, and is used to run data stored in the memory 11 Program code or processing data, such as running the processing system 10, etc.
- the network interface 13 may include a standard wireless network interface and a wired network interface.
- the network interface 13 is usually used to establish a communication connection between the block chain data processing apparatus 1 and other electronic devices.
- the processing system 10 is stored in the memory 11, and includes at least one computer-readable instruction stored in the memory 11, and the at least one computer-readable instruction can be executed by the processor 12 to implement the method of each embodiment of the present application; And, the at least one computer-readable instruction can be divided into different logic modules according to the different functions implemented by its parts.
- the above-mentioned processing system 10 implements the following steps when being executed by the processor 12:
- the monitoring smart contract is called to monitor the system information of the node, and the system information includes the storage capacity of the node;
- the multi-chain data stored on the node is planned according to the chain name, and the multi-chain data with the same chain name is divided into the same pre-created directory in;
- the multi-chain data is deleted.
- the multi-chain data includes block data, index data, status data and historical data.
- system information further includes data status information of multi-chain data, and when the processing system is executed by the processor, the following steps are further implemented:
- the invalid Multi-chain data is planned according to the chain name, and invalid multi-chain data with the same chain name is divided into the same pre-created directory;
- the invalid multi-chain data is deleted.
- the current storage capacity of the node is sent to a predetermined terminal for display and warning.
- FIG. 2 it is a program module diagram of the processing system 10 in FIG. 1 and FIG. 2.
- the processing system 10 is 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.
- the processing system 10 can be divided into: a monitoring module 101, a planning module 102, a synchronization module 103, and a deletion module 104.
- the monitoring module 101 is used for invoking the monitoring smart contract to monitor the system information of the node in the multi-chain scenario of the alliance chain, and the system information includes the storage capacity of the node;
- the monitoring smart contract is used to monitor the node's system information.
- System information includes the storage capacity of the node (that is, the storage capacity of the device used by the node), the data status information of the multi-chain data (that is, whether the data is valid or invalid), and other business information.
- the business information can include the current transaction pen of the blockchain.
- the monitoring of different business information can be customized for different businesses.
- the monitoring process includes: after the node is started, the monitoring smart contract is called to monitor the node, and the subsequent node itself can periodically execute the monitoring smart contract for monitoring.
- a node executes a monitoring smart contract
- conventional system tools can be used for monitoring. For example, on the Linux operating system, use the top and htop commands to monitor memory and CPU usage, use the iostat command to view the usage of data storage devices, and so on.
- the processing system 10 further includes:
- the installation module is used to obtain the smart contract information from the configuration file of the node. If the smart contract information does not include the monitoring smart contract, the monitoring smart contract is installed.
- the processing system 10 further includes:
- the monitoring module is used to call the monitoring smart contract to monitor the system information of the node in the multi-chain scenario of the alliance chain, and the system information includes the storage capacity of the node;
- the planning module is used to plan the multi-chain data stored on the node according to the chain name if it is monitored that the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, and divide the multi-chain data of the same chain name into the same In the pre-created directory;
- the synchronization module is used to send a start message to a predetermined node if there is no transaction currently executing on the node, and after the predetermined node is started, synchronize at least one directory of divided multi-chain data to the predetermined node To expand the capacity of the node;
- the deleting module is used to delete the multi-chain data after receiving the completion message of the predetermined node reading the multi-chain data in the directory.
- the planning module 102 is configured to, if it is monitored that the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, plan the multi-chain data stored on the node according to the chain name, and divide the multi-chain data with the same chain name into In the same pre-created directory;
- multi-chain data includes block data, index data, status data, and historical data.
- the multi-chain data stored on the node is planned according to the chain name (that is, the ledger name), the multi-chain data with the same chain name is divided into the same pre-created directory, and the multi-chain data with different chain names is divided into
- each directory includes all the data of a chain, complete the data file path planning of the multi-chain data in the case of multi-chain, so as to move the data of part of the chain or the data of all the chains to the new node. Realize the expansion of this node.
- the processing system 10 further includes:
- the early warning module if it is monitored that the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, it is used to send the current storage capacity of the node to a predetermined terminal for display and warning.
- the synchronization module 103 is configured to send a start message to a predetermined node if there is no transaction currently executing on the node, and after the predetermined node is started, synchronize at least one directory of divided multi-chain data to the node A predetermined node to expand the capacity of the node;
- the deleting module 104 is configured to delete the multi-chain data after receiving the completion message that the predetermined node reads the multi-chain data in the directory.
- the current node before the expansion of the current node, if the current node does not have a transaction currently being executed, it can send a start message to a predetermined node (that is, a new node), if it is found that the current node is currently executing a transaction, in order to make the transaction If this expansion is not affected, the execution of the transaction will be suspended, and then the start message will be sent to the predetermined node to start the predetermined node to perform the expansion operation.
- a predetermined node that is, a new node
- the predetermined node After the predetermined node receives the start message, it starts. Then, the node synchronizes at least one directory of the divided multi-chain data to the predetermined node. After the predetermined node obtains the directory, it searches and merges Read the data corresponding to the chain name in the directory to this node, and perform the capacity expansion of the cross-chain data. After reading the data corresponding to the chain name in the directory, the predetermined node sends a completion message to the node, After receiving the completion message, the node deletes the corresponding data in the directory synchronized to the predetermined node to release the storage space of the node.
- FIG. 3 is a schematic flowchart of an embodiment of a method for processing blockchain data according to this application. The method is implemented when the processor 13 of the device 1 for processing blockchain data executes the processing system 10 stored in the memory 12 The following steps:
- Step S1 in the multi-chain scenario of the alliance chain, call the monitoring smart contract to monitor the system information of the node, and the system information includes the storage capacity of the node;
- the configuration file includes which chains the node belongs to, the IP address and port information of the node (ie address information), and the smart contract information included in the node.
- the monitoring smart contract can also be a system smart contract, that is, a smart contract built into the system, which exists and can provide services after the blockchain node is created, without additional resources. After the node is started for the first time, the system smart contract is automatically installed to reduce the workload of operation and maintenance.
- system smart contract is automatically installed to reduce the workload of operation and maintenance.
- the monitoring smart contract is used to monitor the node's system information.
- System information includes the storage capacity of the node (that is, the storage capacity of the device used by the node), the data status information of the multi-chain data (that is, whether the data is valid or invalid), and other business information.
- the business information can include the current transaction pen of the blockchain.
- the monitoring of different business information can be customized for different businesses.
- the monitoring process includes: after the node is started, the monitoring smart contract is called to monitor the node, and the subsequent node itself can periodically execute the monitoring smart contract for monitoring.
- the smart contract engine on the node executes the monitoring smart contract, and the monitoring smart contract calls the query interface.
- the smart contract engine reads the current storage capacity of the node through the standard system state collection interface, and returns it to the monitoring smart contract for feedback.
- a node executes a monitoring smart contract
- conventional system tools can be used for monitoring. For example, on the Linux operating system, use the top and htop commands to monitor memory and CPU usage, use the iostat command to view the usage of data storage devices, and so on.
- Step S2 If it is monitored that the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, the multi-chain data stored on the node is planned according to the chain name, and the multi-chain data with the same chain name is divided into the same pre- In the created directory;
- the predetermined first disk capacity is, for example, 80% of the total storage capacity of the node.
- multi-chain data includes block data, index data, status data, and historical data.
- Index data is provided for querying blocks
- status data is a snapshot of data provided to complete business functions
- historical data records the historical information of data modification.
- Block data is stored separately for each chain, but index data, status data, and historical data are stored together.
- the multi-chain data stored on the node is planned according to the chain name (that is, the ledger name), the multi-chain data with the same chain name is divided into the same pre-created directory, and the multi-chain data with different chain names is divided into
- each directory includes all the data of a chain, complete the data file path planning of the multi-chain data in the case of multi-chain, so as to move the data of part of the chain or the data of all the chains to the new node. Realize the expansion of this node.
- the current storage capacity of the node is sent to a predetermined terminal for display and warning.
- the current storage capacity of the node can be converted into a graphical form and sent to a predetermined terminal for display for more intuitive display.
- the current storage capacity of the node is greater than or equal to the predetermined first disk capacity, indicating that the node is currently The storage capacity has reached the bottleneck state, and early warning is needed to take corresponding measures or human intervention.
- Step S3 If there is no transaction currently executing on the node, send a start message to the predetermined node, and after the predetermined node is started, synchronize at least one directory of the divided multi-chain data to the predetermined node , To expand the node;
- Step S4 after receiving the completion message that the predetermined node reads the multi-chain data in the directory, delete the multi-chain data.
- the current node before the expansion of the current node, if the current node does not have a transaction currently being executed, it can send a start message to a predetermined node (that is, a new node), if it is found that the current node is currently executing a transaction, in order to make the transaction If this expansion is not affected, the execution of the transaction will be suspended, and then the start message will be sent to the predetermined node to start the predetermined node to perform the expansion operation.
- a predetermined node that is, a new node
- the predetermined node After the predetermined node receives the start message, it starts. Then, the node synchronizes at least one directory of the divided multi-chain data to the predetermined node. After the predetermined node obtains the directory, it searches and merges Read the data corresponding to the chain name in the directory to this node, and perform the capacity expansion of the cross-chain data. After reading the data corresponding to the chain name in the directory, the predetermined node sends a completion message to the node, After receiving the completion message, the node deletes the corresponding data in the directory synchronized to the predetermined node to release the storage space of the node.
- this application monitors the storage capacity of the node by calling the monitoring smart contract. If the storage capacity of a node reaches the bottleneck, the storage situation of the data node will be modified, and the multi-chain data stored on the node will be The chain name is planned, and the multi-chain data of the same chain name is divided into the same pre-created directory, and the data is stored according to the chain. After the new node is started, the directory is synchronized to the new node. The new node By searching and reading the data corresponding to the chain name in the directory to this node, the application of the capacity expansion scenario is completed, so that the data of part of the chain can be moved to the new node to achieve expansion. This method is simple and efficient to operate. There is no need to synchronize data block by block, which reduces network pressure on other nodes and saves system resources.
- the aforementioned system information further includes data status information of the multi-link data.
- the method further includes:
- the invalid Multi-chain data is planned according to the chain name, and invalid multi-chain data with the same chain name is divided into the same pre-created directory; if there is no transaction currently executing on the node, a start message is sent to the predetermined node, and After the predetermined node is started, the partitioned invalid multi-chain data directory is synchronized to the predetermined node to back up the invalid multi-chain data; when the predetermined node is received, the directory is read After the completion message of the invalid multi-chain data, delete the invalid multi-chain data.
- the predetermined second disk capacity is, for example, 70% of the total storage capacity of the node.
- the node if it is monitored that the current storage capacity of the node is greater than or equal to the predetermined second disk capacity but less than the predetermined first disk capacity, further monitoring whether the node has multi-chain data and the data status information is invalid, that is, whether the data is out of date or When offline, if the data status information of the multi-chain data is invalid, the invalid data can be eliminated, that is, delete directly or delete after backup to further release the storage space of the node.
- node dynamic expansion and data elimination are necessary.
- one node can store data of multiple chains.
- the node Performance bottlenecks may be encountered. Data in some chains can be migrated to other new nodes, and when the data exceeds the validity period or goes offline, old data can be eliminated and hardware resources can be released.
- the embodiments of the present application also propose a computer-readable storage medium, which may be a hard disk, a multimedia card, an SD card, a flash memory card, an SMC, a read-only memory (ROM), an erasable programmable Any one or any combination of read-only memory (EPROM), portable compact disk read-only memory (CD-ROM), USB memory, etc.
- the computer-readable storage medium includes a processing system. For the functions implemented by the processing system when executed by the processor, please refer to the above descriptions of Fig. 2 and Fig. 3, which will not be repeated here.
- the present application also provides a computer-readable storage medium.
- the computer-readable storage medium 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 monitoring smart contract is called to monitor the system information of the node, and the system information includes the storage capacity of the node;
- 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. ⁇
- the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to enable a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present application.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (20)
- 一种区块链数据处理的装置,所述区块链数据处理的装置包括存储器及与所述存储器连接的处理器,所述存储器中存储有可在所述处理器上运行的处理系统,所述处理系统被所述处理器执行时实现如下步骤:在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量;若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点上存储的多链数据按照链名称进行规划,将相同链名称的多链数据划分至相同的预先创建的目录中;若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的多链数据的至少一个目录同步给该预定的节点,以对该节点进行扩容;当接收到该预定的节点读取该目录中的多链数据的完成消息后,删除该多链数据。
- 根据权利要求1所述的区块链数据处理的装置,所述处理器执行所述所述处理系统时,包括以下步骤:所述多链数据包括区块数据、索引数据、状态数据及历史数据。
- 根据权利要求1或2所述的区块链数据处理的装置,所述处理器执行所述处理系统实现所述系统信息还包括多链数据的数据状态信息,在所述在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量之后,还包括以下步骤:若监控到该节点当前的存储容量大于等于预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则将该无效的多链数据进行整合并删除,所述第二磁盘容量小于所述第一磁盘容量;或者若监控到该节点当前的存储容量大于等于该预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则将该无效的多链数据按照链名称进行规划,将相同链名称的无效的多链数据划分至相同的预先创建的目录中;若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的无效的多链数据的目录同步给该预定的节点,以对该无效的多链数据进行备份;当接收到该预定的节点读取该目录中的无效的多链数据的完成消息后,删除该无效的多链数据。
- 根据权利要求1所述的区块链数据处理的装置,所述处理器执行所述处理系统实现在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量之后,还包括以下步骤:若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点当前的存储容量发送给预定的终端进行展示并预警。
- 根据权利要求1所述的区块链数据处理的装置,所述处理器执行所述处理系统实现所述在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量之前,还包括以下步骤:从该节点的配置文件中获取智能合约信息,若该智能合约信息中不包括监控智能合约,则安装监控智能合约。
- 一种区块链数据处理的方法,所述区块链数据处理的方法包括:S1,在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量;S2,若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点上存储的多链数据按照链名称进行规划,将相同链名称的多链数据划分至相同的预先创建的目录中;S3,若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的多链数据的至少一个目录同步给该预定的节点,以对该节点进行扩容;S4,当接收到该预定的节点读取该目录中的多链数据的完成消息后,删除该多链数据。
- 根据权利要求6所述的区块链数据处理的方法,所述多链数据包括区块数据、索引数据、状态数据及历史数据。
- 根据权利要求6或7所述的区块链数据处理的方法,所述系统信息还包括多链数据的数据状态信息,所述步骤S1之后,还包括:若监控到该节点当前的存储容量大于等于预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则 将该无效的多链数据进行整合并删除,所述第二磁盘容量小于所述第一磁盘容量;或者若监控到该节点当前的存储容量大于等于该预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则将该无效的多链数据按照链名称进行规划,将相同链名称的无效的多链数据划分至相同的预先创建的目录中;若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的无效的多链数据的目录同步给该预定的节点,以对该无效的多链数据进行备份;当接收到该预定的节点读取该目录中的无效的多链数据的完成消息后,删除该无效的多链数据。
- 根据权利要求6所述的区块链数据处理的方法,所述步骤S1之后,还包括:若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点当前的存储容量发送给预定的终端进行展示并预警。
- 根据权利要求6所述的区块链数据处理的方法,所述步骤S1之前,还包括:从该节点的配置文件中获取智能合约信息,若该智能合约信息中不包括监控智能合约,则安装监控智能合约。
- 一种处理系统,所述处理系统包括:监控模块,用于在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量;规划模块,用于若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点上存储的多链数据按照链名称进行规划,将相同链名称的多链数据划分至相同的预先创建的目录中;同步模块,用于若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的多链数据的至少一个目录同步给该预定的节点,以对该节点进行扩容;删除模块,用于当接收到该预定的节点读取该目录中的多链数据的完成消息后,删除该多链数据。
- 根据权利要求11所述的处理系统,所述处理系统具体用于:所述多链数据包括区块数据、索引数据、状态数据及历史数据。
- 根据权利要求11或12所述的处理系统,所述处理系统还包括:整合模块,若监控到该节点当前的存储容量大于等于预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则用于将该无效的多链数据进行整合并删除,所述第二磁盘容量小于所述第一磁盘容量;或者划分模块,若监控到该节点当前的存储容量大于等于该预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则用于将该无效的多链数据按照链名称进行规划,将相同链名称的无效的多链数据划分至相同的预先创建的目录中;备份模块,若该节点上当前无执行中的交易,则用于发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的无效的多链数据的目录同步给该预定的节点,以对该无效的多链数据进行备份;处理模块,当接收到该预定的节点读取该目录中的无效的多链数据的完成消息后,用于删除该无效的多链数据。
- 根据权利要求11所述的处理系统,所述处理系统还包括:预警模块,若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则用于将该节点当前的存储容量发送给预定的终端进行展示并预警。
- 根据权利要求11所述的处理系统,所述处理系统还包括:安装模块,用于从该节点的配置文件中获取智能合约信息,若该智能合约信息中不包括监控智能合约,则安装监控智能合约。
- 一种计算机可读存储介质,所述计算机可读存储介质中存储计算机指令,当所述计算机指令在计算机上运行时,使得计算机执行如下步骤:S1,在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量;S2,若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点上存储的多链数据按照链名称进行规划,将相同链名称的多链数据划分至相同的预先创建的目录中;S3,若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的多链数据的至少一个目录同步给该预定的节点,以对该节点进行扩容;S4,当接收到该预定的节点读取该目录中的多链数据的完成消息后,删除该多链数据。
- 根据权利要求16所述的计算机可读存储介质,当所述计算机指令在所述计算机上运行所述区块链数据处理的方法时,使得所述计算机执行如下步骤:所述多链数据包括区块数据、索引数据、状态数据及历史数据。
- 根据权利要求16或17所述的计算机可读存储介质,当所述计算机指令在所述计算机上运行所述S1,在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量之后,使得所述计算机还执行如下步骤:若监控到该节点当前的存储容量大于等于预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则将该无效的多链数据进行整合并删除,所述第二磁盘容量小于所述第一磁盘容量;或者若监控到该节点当前的存储容量大于等于该预定的第二磁盘容量且小于所述第一磁盘容量,且监控到该节点的有多链数据的数据状态信息为无效时,则将该无效的多链数据按照链名称进行规划,将相同链名称的无效的多链数据划分至相同的预先创建的目录中;若该节点上当前无执行中的交易,则发送启动消息给预定的节点,并在该预定的节点启动后,将经划分后的无效的多链数据的目录同步给该预定的节点,以对该无效的多链数据进行备份;当接收到该预定的节点读取该目录中的无效的多链数据的完成消息后,删除该无效的多链数据。
- 根据权利要求16所述的计算机可读存储介质,当所述计算机指令在所述计算机上运行所述S1,在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量之后,使得所述计算机还执行如下步骤:若监控到该节点当前的存储容量大于等于预定的第一磁盘容量,则将该节点当前的存储容量发送给预定的终端进行展示并预警。
- 根据权利要求16所述的计算机可读存储介质,当所述计算机指令在所 述计算机上运行所述S1,在联盟链的多链场景中,调用监控智能合约对节点的系统信息进行监控,所述系统信息包括该节点的存储容量时,使得所述计算机还执行如下步骤:用于从该节点的配置文件中获取智能合约信息,若该智能合约信息中不包括监控智能合约,则安装监控智能合约。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910371198.7A CN110209736A (zh) | 2019-05-06 | 2019-05-06 | 区块链数据处理的装置、方法及存储介质 |
CN201910371198.7 | 2019-05-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020224236A1 true WO2020224236A1 (zh) | 2020-11-12 |
Family
ID=67786884
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/120589 WO2020224236A1 (zh) | 2019-05-06 | 2019-11-25 | 区块链数据处理的装置、方法、系统及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110209736A (zh) |
WO (1) | WO2020224236A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115841285A (zh) * | 2022-11-28 | 2023-03-24 | 浙江百世技术有限公司 | 基于区块链的商品物流追溯方法及系统 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110209736A (zh) * | 2019-05-06 | 2019-09-06 | 深圳壹账通智能科技有限公司 | 区块链数据处理的装置、方法及存储介质 |
CN112631994A (zh) * | 2020-12-29 | 2021-04-09 | 深圳市商汤科技有限公司 | 数据迁移方法及系统 |
CN113407626B (zh) * | 2021-06-16 | 2024-05-10 | 深圳大学 | 一种基于区块链的规划管控方法、存储介质及终端设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107453896A (zh) * | 2017-06-27 | 2017-12-08 | 阿里巴巴集团控股有限公司 | 多重区块链网络数据处理方法、装置及服务器 |
CN107832139A (zh) * | 2017-09-26 | 2018-03-23 | 上海点融信息科技有限责任公司 | 用于管理区块链节点的计算资源的方法、设备和系统 |
CN108829350A (zh) * | 2018-05-31 | 2018-11-16 | 阿里巴巴集团控股有限公司 | 基于区块链的数据迁移方法和装置 |
US20190066101A1 (en) * | 2017-08-22 | 2019-02-28 | Sap Se | Transaction Platform Providing Unified View on Multiple Heterogeneous Blockchains |
CN110209736A (zh) * | 2019-05-06 | 2019-09-06 | 深圳壹账通智能科技有限公司 | 区块链数据处理的装置、方法及存储介质 |
-
2019
- 2019-05-06 CN CN201910371198.7A patent/CN110209736A/zh active Pending
- 2019-11-25 WO PCT/CN2019/120589 patent/WO2020224236A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107453896A (zh) * | 2017-06-27 | 2017-12-08 | 阿里巴巴集团控股有限公司 | 多重区块链网络数据处理方法、装置及服务器 |
US20190066101A1 (en) * | 2017-08-22 | 2019-02-28 | Sap Se | Transaction Platform Providing Unified View on Multiple Heterogeneous Blockchains |
CN107832139A (zh) * | 2017-09-26 | 2018-03-23 | 上海点融信息科技有限责任公司 | 用于管理区块链节点的计算资源的方法、设备和系统 |
CN108829350A (zh) * | 2018-05-31 | 2018-11-16 | 阿里巴巴集团控股有限公司 | 基于区块链的数据迁移方法和装置 |
CN110209736A (zh) * | 2019-05-06 | 2019-09-06 | 深圳壹账通智能科技有限公司 | 区块链数据处理的装置、方法及存储介质 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115841285A (zh) * | 2022-11-28 | 2023-03-24 | 浙江百世技术有限公司 | 基于区块链的商品物流追溯方法及系统 |
CN115841285B (zh) * | 2022-11-28 | 2023-09-19 | 浙江百世技术有限公司 | 基于区块链的商品物流追溯方法及系统 |
Also Published As
Publication number | Publication date |
---|---|
CN110209736A (zh) | 2019-09-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020224236A1 (zh) | 区块链数据处理的装置、方法、系统及存储介质 | |
US11397648B2 (en) | Virtual machine recovery method and virtual machine management device | |
WO2020207010A1 (zh) | 数据备份方法、装置及计算机可读存储介质 | |
WO2019085471A1 (zh) | 数据库同步方法、应用服务器及计算机可读存储介质 | |
US8756199B2 (en) | File level hierarchical storage management system, method, and apparatus | |
KR20210002574A (ko) | 데이터 백업 방법, 저장 매체 및 컴퓨팅 기기 | |
US7681001B2 (en) | Storage system | |
CN110659259B (zh) | 数据库迁移方法、服务器以及计算机存储介质 | |
US20120278429A1 (en) | Cluster system, synchronization controlling method, server, and synchronization controlling program | |
US20100153346A1 (en) | Data integrity in a database environment through background synchronization | |
WO2020015116A1 (zh) | 数据库监控方法及终端设备 | |
WO2020224100A1 (zh) | 区块链配置文件的处理装置、系统、方法及存储介质 | |
CN110597887A (zh) | 一种基于区块链网络的数据管理方法、装置及存储介质 | |
US20160139996A1 (en) | Methods for providing unified storage for backup and disaster recovery and devices thereof | |
JP6583975B1 (ja) | データ処理装置、データ処理方法及びプログラム | |
WO2024131057A1 (zh) | 获取文件系统差异数据的方法、装置、设备及介质 | |
WO2018010603A1 (zh) | 基于视频云存储系统的存储模式升级方法、装置和系统 | |
CN112711606A (zh) | 数据库访问方法、装置、计算机设备和存储介质 | |
WO2020020170A1 (zh) | 数据删除方法和装置 | |
EP3082050A1 (en) | Mass data fusion storage method and system | |
CN112764973B (zh) | 数据容灾方法、装置、电子设备和可读存储介质 | |
US11886439B1 (en) | Asynchronous change data capture for direct external transmission | |
JP6292796B2 (ja) | 情報処理装置、情報処理方法及びプログラム | |
CN108848136B (zh) | 一种云服务集群的共享存储方法 | |
CN102724080B (zh) | 网络管理系统及方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19927613 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19927613 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 18/03/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19927613 Country of ref document: EP Kind code of ref document: A1 |