Distributed database version information management method and device, electronic equipment and medium

Abstract

The application provides a distributed database version information management method and device, electronic equipment and medium, and relates to the field of distributed database operation and maintenance. The method comprises the following steps: creating a target component product package required by a distributed database, and adding a version information file in the target component product package; in response to an event that the target component product package is successfully installed, establishing a communication connection between a component operation and maintenance agent service and an operation and maintenance service of the distributed database; reading component version information from the version information file of the target component product package through the component operation and maintenance agent service, and sending the component version information to the operation and maintenance service; and storing the received component version information in a target data table through the operation and maintenance service. The application scheme realizes operation and maintenance management of the version information of each component of the distributed database.

Description

Technical Field

[0001] This invention relates to the field of distributed database operation and maintenance, and specifically to a method, apparatus, electronic device, and storage medium for managing version information of a distributed database. Background Technology

[0002] With the advent of the data era, databases, as a crucial infrastructure, play a key role in various fields. The combination of databases and network technologies has given rise to distributed databases. Distributed database platforms provide unified database services through a shared-nothing architecture and achieve horizontal scaling of database capabilities by adding database nodes. Summary of the Invention

[0003] This invention provides a method, apparatus, electronic device, and storage medium for managing version information of a distributed database.

[0004] According to one aspect of the present invention, a method for managing version information of a distributed database is provided, comprising:

[0005] Create the target component product package required for the distributed database, and add version information files to the target component product package;

[0006] In response to the successful installation of the target component product package, a communication connection is established between the component operation and maintenance agent service and the operation and maintenance service of the distributed database.

[0007] The component operation and maintenance agent service reads the component version information from the version information file of the target component product package and sends it to the operation and maintenance service.

[0008] The received component version information is stored in the target data table through the operation and maintenance service.

[0009] According to another aspect of the present invention, a distributed database version information management device is provided, comprising:

[0010] The component creation module is used to create the target component product package required by the distributed database and add version information files to the target component product package;

[0011] The connection module is used to establish a communication connection between the component operation and maintenance agent service and the operation and maintenance service of the distributed database in response to the successful installation of the target component product package.

[0012] The version information reading module is used to read component version information from the version information file of the target component product package through the component operation and maintenance agent service, and send it to the operation and maintenance service.

[0013] The storage module is used to store the received component version information in the target data table through the operation and maintenance service.

[0014] According to another aspect of the present invention, an electronic device is provided, comprising:

[0015] At least one processor; and

[0016] A memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the distributed database version information management method according to any embodiment of the present invention.

[0018] According to another aspect of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, the computer instructions being used to cause a computer to execute the distributed database version information management method described in any embodiment of the present invention.

[0019] According to the technology of the present invention, no manual modification is required when the version of the distributed database component is updated, which overcomes the problem of chaotic version management of the original operation and maintenance upgrade. It not only facilitates the later operation and maintenance of developers, but also allows users to directly view the version number information of the currently used component on the interface.

[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating a distributed database version information management method according to an embodiment of the present invention;

[0023] Figure 2a This is a flowchart illustrating another distributed database version information management method according to an embodiment of the present invention;

[0024] Figure 2bThis is a logical diagram illustrating version information synchronization through an operation and maintenance interface, component operation and maintenance agent service, and operation and maintenance service, according to an embodiment of the present invention.

[0025] Figure 3 This is a flowchart illustrating another distributed database version information management method according to an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of a distributed database version information management device according to an embodiment of the present invention;

[0027] Figure 5 This is a block diagram of an electronic device used to implement the distributed database version information management method of this invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] The distributed database in this invention typically consists of multiple components. With the continuous development and advancement of information technology, and the needs of practical application scenarios, it is necessary to upgrade the internal components of the distributed database. However, due to the complexity of actual production environments, version number management of different components often becomes chaotic, causing significant inconvenience for later version updates and operation and maintenance. Therefore, this invention proposes a convenient and reliable method for managing distributed database version numbers. The specific process of this method can be found in the following embodiments.

[0030] Figure 1 This is a flowchart illustrating a distributed database version information management method according to an embodiment of the present invention. This embodiment is applicable to situations involving the management of version information of a distributed database, wherein the version information of the distributed database is composed of the component version information of each component in the distributed database. This method can be executed by a distributed database version information management device, which is implemented in software and / or hardware, preferably configured in an electronic device.

[0031] like Figure 1 As shown, the method specifically includes the following:

[0032] S101. Create the target component product package required for the distributed database, and add version information files to the target component product package.

[0033] In this embodiment, the target component product package can be an update package of a component or a newly developed functional component; no specific limitation is made here. For example, taking an update package of a component as an example, the purpose of creating the target component product package is to iteratively update the corresponding component in the distributed database. Before creating the target component product package required for the distributed database, the branch to be built and the artifact repository path where the component is located are selected. Based on this, when creating the target component product package, the configuration or method required to build the target component product package is set through a file in a preset format (e.g., an XML file); then, the continuous integration tool Jenkins executes this XML file to build the corresponding component product package. In this embodiment, the continuous integration tool Jenkins can also be used to write the code build round, component name, component branch name, and build time of the target component product as component version information into the version information file; the version information file is added to the target component product package. Further, according to the pre-selected artifact repository address, the built target component product package is sent to the corresponding artifact repository for compilation, packaging, and other operations. It should be noted that in this embodiment, the version information file is added to the component product package so that the version information is combined with the product build, thus preventing the component version information from being tampered with.

[0034] S102. In response to the successful installation of the target component product package, establish a communication connection between the component operation and maintenance agent service and the operation and maintenance service of the distributed database.

[0035] In this embodiment, after constructing the target component product package, it can be installed in the distributed database to enable component updates and iterations. Furthermore, after successful installation of the target component product package, a communication connection is established between the component operation and maintenance agent service and the operation and maintenance service of the distributed database. For example, a Netty channel is established between the component operation and maintenance agent service and the operation and maintenance service to synchronize and update the version information of the distributed database. The component operation and maintenance agent service is used to parse and obtain the component version information; the operation and maintenance service is used to manage the component version information, such as storing or displaying it. Specifically, the component version information synchronization process is described in steps S103-S104.

[0036] S103. The component version information is read from the version information file of the target component product package through the component operation and maintenance agent service, and sent to the operation and maintenance service.

[0037] S104. The received component version information is stored in the target data table through the operation and maintenance service.

[0038] In this embodiment, for components in the distributed database, after the component is installed, the component version information of each component is stored in a designated folder, such as the etc folder in the user's home directory of each component. The component operation and maintenance agent service can then obtain the version information file from the etc folder in the target component's user home directory, parse the version information file to obtain the corresponding component version information, and then send the obtained component version information to the operation and maintenance service, for example, through a pre-created Netty channel. The operation and maintenance service will then store the received component version information in a target data table, where the target data table can be any pre-specified data table, without specific limitations here.

[0039] In this embodiment, after a component is upgraded, its version information is automatically synchronized and saved, thus realizing the operation and maintenance management of the version information of each component of the distributed database.

[0040] Furthermore, the operation and maintenance service also provides a display function. This function allows the version information of components stored in the target data table to be displayed on a pre-defined operation and maintenance interface for operation and maintenance personnel to view. It should be noted that the operation and maintenance interface can also display all historical version information, version update time, and important time records (such as records of fixing key issues) for each component, providing operation and maintenance personnel with detailed version information. Thus, through the display function provided by the operation and maintenance service, operation and maintenance personnel can directly view the version information of each component of the distributed database on the interface.

[0041] Figure 2a This is a flowchart illustrating another distributed database version information management method according to an embodiment of the present invention. In this embodiment, the operation and maintenance interface also provides a function for users to actively trigger component version information synchronization updates. Based on this, operation and maintenance personnel can achieve automatic synchronization of version information of various components of the distributed database through touch operations on the operation and maintenance interface. Figure 2a As shown, this distributed database version information management method specifically includes the following steps:

[0042] S201. Generate a version information synchronization request based on the touch operation of the operation and maintenance personnel on the operation and maintenance interface.

[0043] S202. In response to the version information synchronization request, the component version information is read from the version information file of the specified component through the component operation and maintenance agent service and sent to the operation and maintenance service.

[0044] S203. The received component version information is stored in the target data table through the operation and maintenance service.

[0045] In this embodiment, the operation and maintenance interface provides at least one control for synchronizing database version information. Operation and maintenance personnel can actively trigger the synchronization of component version information of the distributed database components by touching this control. In specific implementation, a version information synchronization request can be generated based on the touch operation of the operation and maintenance personnel on the operation and maintenance interface. The version information synchronization request includes at least one specified component whose version information needs to be synchronized.

[0046] Upon receiving a version information synchronization request, the component operation and maintenance agent service retrieves the version information file from the "etc" folder in the home directory of the specified component user, parses the file to obtain the component version information, and then sends the obtained component version information to the operation and maintenance service. The operation and maintenance service then stores the received component version information in the target data table.

[0047] For clarity, see [link to documentation]. Figure 2b This document illustrates the logic diagram for version information synchronization through an operations and maintenance (O&M) interface, a component O&M agent service, and an O&M operation and maintenance service. Optionally, the O&M interface generates a version information synchronization request for multiple specified components via touch operations by O&M personnel. This request is then sent to the O&M operation and maintenance service, which in turn sends a synchronized version information event generated based on the synchronization request to the component O&M agent service via the Netty channel. The component O&M agent service reads the component version information file of the specified component, assembles the obtained component version information into a message, and sends it back to the O&M operation and maintenance service. The O&M operation and maintenance service updates the version information to the database based on the received message and simultaneously displays the update result on the O&M interface. This provides a clear and intuitive view of the version information for O&M personnel.

[0048] Figure 3 This is a flowchart illustrating another distributed database version information management method according to an embodiment of the present invention. Figure 3 As shown, the method specifically includes the following:

[0049] S301. Create the target component product package required for the distributed database, and add version information files to the target component product package.

[0050] In this embodiment, the target component product package can be an update package of a component or a newly developed functional component; no specific limitation is made here. For example, taking an update package of a component as an example, the purpose of creating the target component product package is to iteratively update the corresponding component in the distributed database. Before creating the target component product package required for the distributed database, the branch to be built and the artifact repository path where the component is located are selected. Based on this, when creating the target component product package, the configuration or method required to build the target component product package is set through a file in a preset format (e.g., an XML file); then, the continuous integration tool Jenkins executes this XML file to build the corresponding component product package. In this embodiment, the continuous integration tool Jenkins can also be used to write the code build round, component name, component branch name, and build time of the target component product as component version information into the version information file; the version information file is added to the target component product package. Further, according to the pre-selected artifact repository address, the built target component product package is sent to the corresponding artifact repository for compilation, packaging, and other operations. It should be noted that in this embodiment, the version information file is added to the component product package so that the version information is combined with the product build, thus preventing the component version information from being tampered with.

[0051] S302. Before installing the target component product package, verify the version information of the target component product package, and if the verification fails, intercept the installation of the target component product package; if the verification is successful, proceed to step S303.

[0052] In this embodiment, to prevent components that are inconsistent with the current version information of the database from being installed, which would cause confusion in the database version information, the version information of the target component product package is verified before installation. For example, the version information of the target component product package is verified to be consistent with the current version information of the database. If they are consistent, the subsequent steps are executed; otherwise, the installation of the target component product package is blocked.

[0053] S303. In response to the successful installation of the target component product package, establish a communication connection between the component operation and maintenance agent service and the operation and maintenance service of the distributed database.

[0054] In this embodiment, after constructing the target component product package, it can be installed in the distributed database to enable component updates and iterations. Furthermore, after successful installation of the target component product package, a communication connection is established between the component operation and maintenance agent service and the operation and maintenance service of the distributed database. For example, a Netty channel is established between the component operation and maintenance agent service and the operation and maintenance service to synchronize and update the version information of the distributed database. The component operation and maintenance agent service is used to parse and obtain the component version information; the operation and maintenance service is used to manage the component version information, such as storing or displaying it.

[0055] S304. The component version information is read from the version information file of the target component product package through the component operation and maintenance agent service, and sent to the operation and maintenance service.

[0056] S305. The received component version information is stored in the target data table through the operation and maintenance service.

[0057] In this embodiment, for components in the distributed database, after the component is installed, the component version information of each component is stored in a designated folder, such as the etc folder in the user's home directory of each component. The component operation and maintenance agent service can then obtain the version information file from the etc folder in the target component's user home directory, parse the version information file to obtain the corresponding component version information, and then send the obtained component version information to the operation and maintenance service, for example, through a pre-created Netty channel. The operation and maintenance service will then store the received component version information in a target data table, where the target data table can be any pre-specified data table, without specific limitations here.

[0058] In this embodiment, the version information of the target component product package is verified before installation. Only after the verification is passed can the package be installed and subsequent version information synchronization be performed. This can prevent components that are inconsistent with the current version information in the database from being installed, which would cause the database version information to become chaotic.

[0059] Figure 4 This is a schematic diagram of a distributed database version information management device according to an embodiment of the present invention. This embodiment is applicable to scenarios where version information of a distributed database is managed. Figure 4 As shown, the device 400 specifically includes:

[0060] The component creation module 401 is used to create the target component product package required by the distributed database, and to add version information files to the target component product package;

[0061] Connection module 402 is used to establish a communication connection between the component operation and maintenance agent service and the operation and maintenance service of the distributed database in response to the successful installation of the target component product package;

[0062] The version information reading module 403 is used to read component version information from the version information file of the target component product package through the component operation and maintenance agent service, and send it to the operation and maintenance service.

[0063] Storage module 404 is used to store the received component version information in the target data table through the operation and maintenance service.

[0064] Based on the above embodiments, optionally, the component creation module includes:

[0065] The version information generation unit is used to write the code build round, component name, component branch name and build time of the target component product as component version information into the version information file through the continuous integration tool Jenkins;

[0066] An information adding unit is used to add the version information file to the target component product package.

[0067] In addition to the above embodiments, optionally, the following further includes:

[0068] The display module is used to display the component version information stored in the target data table in a preset operation and maintenance interface so that operation and maintenance personnel can view it.

[0069] In addition to the above embodiments, optionally, the following further includes:

[0070] The request generation module is used to generate a version information synchronization request based on the touch operation of the operation and maintenance personnel on the operation and maintenance interface; wherein, the version information synchronization request includes at least one specified component that needs to synchronize version information;

[0071] The request and response module is used to respond to the version information synchronization request by reading the component version information from the version information file of the specified component through the component operation and maintenance agent service and sending it to the operation and maintenance service.

[0072] The storage module is used to store the received component version information in the target data table through the operation and maintenance service.

[0073] In addition to the above embodiments, optionally, the following further includes:

[0074] The verification module is used to verify the version information of the target component product package before installation, and to intercept the installation of the target component product package if the verification fails.

[0075] Based on the above embodiments, optionally, the version information of the distributed database is composed of the component version information of each component in the distributed database.

[0076] The above-described products can perform the methods provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects for performing the methods.

[0077] The collection, storage, use, processing, transmission, provision, and invention of user personal information involved in the technical solution of this invention all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0078] According to embodiments of the present invention, the present invention also provides an electronic device, a readable storage medium, and a computer program product.

[0079] Figure 5 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0080] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0081] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0082] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as performing a distributed database version information management method.

[0083] In some embodiments, the distributed database version information management method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the distributed database version information management method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the distributed database version information management method by any other suitable means (e.g., by means of firmware).

[0084] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0085] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable distributed database version information management device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0086] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0087] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0088] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0089] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0090] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

Claims

1. A method for managing version information in a distributed database, characterized in that, include: Create the target component product package required for the distributed database, and use the continuous integration tool Jenkins to write the code build round, component name, component branch name, and build time of the target component product as component version information into a version information file; wherein, the version information file is composed of the component version information of each component in the distributed database; Add the version information file to the target component product package; In response to the successful installation of the target component product package, a communication connection is established between the component operation and maintenance agent service and the operation and maintenance service of the distributed database. The component operation and maintenance agent service reads the component version information from the version information file of the target component product package and sends it to the operation and maintenance service. The received component version information is stored in the target data table through the operation and maintenance service.

2. The method according to claim 1, characterized in that, Also includes: The component version information stored in the target data table is displayed in a preset operation and maintenance interface for operation and maintenance personnel to view.

3. The method according to claim 2, characterized in that, Also includes: Based on the touch operation of the operation and maintenance personnel on the operation and maintenance interface, a version information synchronization request is generated; wherein, the version information synchronization request includes at least one specified component that needs to synchronize version information; In response to the version information synchronization request, the component version information is read from the version information file of the specified component through the component operation and maintenance agent service and sent to the operation and maintenance service. The received component version information is stored in the target data table through the operation and maintenance service.

4. The method according to claim 1, characterized in that, Also includes: Before installing the target component product package, the version information of the target component product package is verified, and if the verification fails, the installation of the target component product package is blocked.

5. The method according to claim 1, characterized in that, The version information of the distributed database is composed of the component version information of each component in the distributed database.

6. A distributed database version information management device, characterized in that, include: The component creation module is used to create the target component product package required by the distributed database and add version information files to the target component product package; The connection module is used to establish a communication connection between the component operation and maintenance agent service and the operation and maintenance service of the distributed database in response to the successful installation of the target component product package. The version information reading module is used to read component version information from the version information file of the target component product package through the component operation and maintenance agent service, and send it to the operation and maintenance service. The storage module is used to store the received component version information in the target data table through the operation and maintenance service; The component creation module includes: The version information generation unit is used to write the code build round, component name, component branch name, and build time of the target component product as component version information into a version information file through the continuous integration tool Jenkins; wherein, the version information file is composed of the component version information of each component in the distributed database; An information adding unit is used to add the version information file to the target component product package.

7. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the distributed database version information management method according to any one of claims 1-5.

8. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to execute the distributed database version information management method according to any one of claims 1-5.

Images