Distributed database transaction information visualization method and device, equipment and storage medium

Abstract

The invention relates to the technical field of distributed databases, in particular to a distributed database transaction information visualization method and device, equipment and a storage medium, and the method comprises the following steps: generating a query condition based on obtained node filtering information, and querying component information corresponding to the query condition from a preset metadata node; wherein the node filtering information comprises a target filtering cluster and a target filtering node; based on the query condition and the component information, collecting transaction information under each target filtering node corresponding to the node filtering information to obtain a target transaction information set; and displaying the target transaction information set in the form of a data table. The efficiency of analyzing the cause of the problem of the transaction by the operation and maintenance personnel can be improved.

Description

Technical Field

[0001] This application relates to the field of distributed database technology, and in particular to a method, apparatus, device and storage medium for visualizing distributed database transaction information. Background Technology

[0002] In modern computer systems, distributed databases have become a core infrastructure for enterprise applications due to their high availability, scalability, and fault tolerance. As business scales up, distributed databases need to handle high-concurrency transactions. A transaction typically involves a certain number of compute nodes and data nodes. Each compute node and data node has a system table that records the execution status of a transaction on its respective node.

[0003] When a transaction encounters a problem, operations and maintenance personnel need to check the transaction execution status recorded in the system tables of each node involved in the transaction, and then analyze the cause of the transaction problem. Since the number of system tables involved in a transaction is generally large, and operations and maintenance personnel need to correlate the transaction execution status recorded in each system table to analyze the cause of the transaction problem, the efficiency of analyzing the cause of the transaction problem is low. Summary of the Invention

[0004] To improve the efficiency of operations and maintenance personnel in analyzing the causes of transaction problems, this application provides a method, apparatus, device, and storage medium for visualizing distributed database transaction information.

[0005] Firstly, this application provides a method for visualizing distributed database transaction information, including:

[0006] Based on the obtained node filtering information, query conditions are generated, and component information corresponding to the query conditions is queried from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node;

[0007] Based on the query conditions and the component information, transaction information under each target filter node corresponding to the node filter information is collected to obtain a target transaction information set;

[0008] The target transaction information set is displayed in the form of a data table.

[0009] Secondly, this application provides a distributed database transaction information visualization device, comprising:

[0010] The information filtering module is used to generate query conditions based on the acquired node filtering information, and query component information corresponding to the query conditions from preset metadata nodes; wherein, the node filtering information includes target filtering clusters and target filtering nodes;

[0011] The information collection module is used to collect transaction information under each target filter node corresponding to the node filter information based on the query conditions and the component information, so as to obtain a target transaction information set;

[0012] The information display module is used to display the target transaction information set in the form of a data table.

[0013] Thirdly, this application provides a computer device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the method described above.

[0014] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method.

[0015] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0016] The aforementioned distributed database transaction information visualization method, apparatus, device, and storage medium generate query conditions based on acquired node filtering information and query component information corresponding to the query conditions from preset metadata nodes. The node filtering information includes target filtering clusters and target filtering nodes. Based on the query conditions and the component information, transaction information under each target filtering node corresponding to the node filtering information is collected to obtain a target transaction information set. The target transaction information set is displayed in the form of a data table. Through the above implementation, by using query conditions and component information, transaction information under each target filtering node of the target filtering cluster in the query conditions can be collected, and then the collected transaction information is uniformly displayed in the form of a data table. Thus, when a transaction encounters a problem, maintenance personnel can simultaneously view and analyze the transaction information under all nodes corresponding to that transaction, as displayed in the data table, thereby improving the efficiency of maintenance personnel in analyzing the causes of transaction problems.

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

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart of a distributed database transaction information visualization method provided in the embodiments of this application;

[0020] Figure 2 This is a schematic diagram of the structure of a distributed database transaction information visualization device provided in an embodiment of this application;

[0021] Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application;

[0022] Figure 4 This is an internal structural diagram of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this disclosure.

[0024] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings herein are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0025] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0026] Example 1

[0027] Figure 1 This is a flowchart of a distributed database transaction information visualization method provided in Embodiment 1 of this application, with reference to... Figure 1 The method can be executed by a device that performs the method, which can be implemented in software and / or hardware, and the method includes:

[0028] S110. Generate query conditions based on the acquired node filtering information, and query the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0029] It should be noted that distributed databases are often used to handle high-concurrency transactions. For example, the transactions that a distributed database handles include adding, deleting, modifying, and querying stored data, etc., without being limited to any specific type. In some cases, due to limited server computing resources or server failures, transaction problems may occur, such as deadlocks or long transaction execution times. In these cases, operations and maintenance personnel need to obtain the transaction information to analyze the cause of the transaction problems. In other cases, operations and maintenance personnel also need to obtain the transaction information to determine whether the execution of the transaction meets expectations. The transaction information includes: a globally unique identifier for the transaction, the transaction execution status, the transaction execution duration, and the transaction session number, etc., without being limited to any specific type. The transaction execution status includes: running, waiting for locks, committed, and rolled back.

[0030] A distributed database comprises multiple compute nodes and multiple data nodes. Compute nodes focus on "computational logic processing," responsible for receiving user requests, parsing SQL, generating execution plans, coordinating task scheduling, summarizing intermediate results returned by data nodes, and finally returning the results to the user. Data nodes focus on "data storage and local computation," responsible for actually storing sharded data (data fragments split according to a distributed strategy), maintaining data replicas (ensuring high availability), and executing local computation tasks (such as filtering, aggregation, and index queries) issued by compute nodes. A transaction may involve multiple compute nodes and data nodes during execution. In a distributed database, each compute node or data node belongs to a corresponding node cluster, and each node cluster includes multiple compute nodes and data nodes.

[0031] When a transaction encounters a problem, it's necessary to first filter out the transaction information across all nodes in the node cluster involved in that transaction for unified display later. This requires filtering out the nodes corresponding to the transaction and the node clusters they belong to. In response to a transaction problem, operations personnel can query the nodes corresponding to that transaction and the node clusters they belong to. They then input the queried nodes and node clusters into the query box of the information visualization system. The nodes input into the query box are designated as target filter nodes, and the node clusters input into the query box are designated as target filter clusters. Both target filter nodes and target filter clusters are collectively referred to as node filter information. The information visualization system processes the input node filter information to obtain the query conditions.

[0032] The information visualization system includes a metadata node. Query conditions are input into this metadata node to retrieve component information corresponding to the query conditions. The component information consists of node information corresponding to each target filtering node. For example, the node information includes: node ID, node port, host IP, username, and password. In other embodiments, the specific details are not limited.

[0033] S120. Based on the query conditions and the component information, collect the transaction information under each target filter node corresponding to the node filter information to obtain the target transaction information set.

[0034] The information visualization system can collect transaction information of all transactions involving each target filter node based on the query conditions and component information obtained in the above steps, and record the collected transaction information as the target transaction information set.

[0035] S130. Display the target transaction information set in the form of a data table.

[0036] To facilitate intuitive viewing of the target transaction information set by operations and maintenance personnel, this embodiment displays the target transaction information set in the form of a data table. Each field of the data table corresponds one-to-one with each component of the transaction information set. For example, the fields of the data table include: transaction UUID (globally unique identifier of the transaction), TSN (transaction serial number), GTID (global transaction ID), transaction status, execution duration (ms), currently executing SQL (SQL statement used to execute the transaction), username, CN identifier, execution thread number, client IP:PORT, session number, start time, and service port. In other embodiments, the specific details are not limited.

[0037] It should be noted that this embodiment generates query conditions based on the acquired node filtering information, and queries the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering nodes; based on the query conditions and the component information, transaction information under each of the target filtering nodes corresponding to the node filtering information is collected to obtain the target transaction information set; the target transaction information set is displayed in the form of a data table; through the above implementation, by using query conditions and component information, transaction information under each target filtering node under the target filtering cluster in the query conditions can be collected, and then the collected transaction information is uniformly displayed in the form of a data table. In this way, when a transaction has a problem, the operation and maintenance personnel can simultaneously view and analyze the transaction information under all nodes corresponding to the transaction displayed in the data table, thereby improving the efficiency of the operation and maintenance personnel in analyzing the cause of the transaction problem.

[0038] Example 2

[0039] This application provides a distributed database transaction information visualization method in Embodiment 2. This method optimizes the "collecting transaction information under each target filter node corresponding to the node filter information based on the query conditions and the component information to obtain a target transaction information set" in Embodiment 1. It should be noted that for parts not described in detail in this embodiment, please refer to the descriptions in other embodiments. The method includes:

[0040] S210. Generate query conditions based on the acquired node filtering information, and query the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0041] S221. Based on the query conditions and the component information, generate a transaction information collection instruction.

[0042] In this system, after obtaining the query conditions and component information, the information visualization system needs to collect transaction information related to the transactions of each target filtering node in the query conditions. It should be noted that the information visualization system communicates with a node connection pool that manages nodes in a unified distributed database; this information visualization system is also known as a host agent. To control this host agent to collect transaction information related to the transactions of each target filtering node in the query conditions, a corresponding collection command needs to be sent to it. In this embodiment, the information visualization system can assemble the aforementioned query conditions and component information into a collection command in a certain format, and record this collection command as a transaction information collection instruction.

[0043] S222. Determine the host agent corresponding to the component information.

[0044] It should be noted that the information visualization system may have multiple host proxies in communication connection, and it is necessary to determine the host proxy used to collect transaction information involving each target filtering node in the query conditions; among them, the component information includes the host IP, which is used to identify the IP of the host proxy to be determined.

[0045] Specifically, the information visualization system first parses the host IP from the component information, and then determines the corresponding host proxy through the host IP.

[0046] S223. Based on the host agent, collect the transaction information under each target filtering node corresponding to the transaction information collection instruction to obtain the target transaction information set.

[0047] The information visualization system sends transaction information collection instructions to the host agent, which can control the host agent to collect transaction information involving each target filter node in the query conditions, and the collected transaction information is collectively referred to as the target transaction information set. Furthermore, the host agent assembles the target transaction information set in a predetermined format and feeds back the assembled target transaction information set to the information visualization system.

[0048] S230. Display the target transaction information set in the form of a data table.

[0049] Example 3

[0050] This application provides a distributed database transaction information visualization method in Embodiment 3. This method optimizes the "collecting transaction information under each target filtering node corresponding to the node filtering information based on the query conditions and the component information to obtain a target transaction information set" in Embodiment 1. It should be noted that the node filtering information also includes: target filtering transactions. For parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes:

[0051] S310. Generate query conditions based on the acquired node filtering information, and query the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0052] S321. Based on the query conditions and the component information, generate a transaction information collection instruction.

[0053] S322. Determine the host agent corresponding to the component information.

[0054] S323. Based on the host agent, collect transaction information under each target filtered transaction corresponding to the transaction information collection instruction to obtain the target transaction information set.

[0055] It should be noted that node filtering information can be processed into query conditions, and these query conditions can be combined with component information to construct transaction information collection instructions. In the scheme shown in Example 1, the node filtering information only includes the target filtering cluster and the target filtering node. Therefore, the target transaction information set collected subsequently through the corresponding transaction information collection instructions is the transaction information of all transactions involving the target filtering node. However, all transactions involving the target filtering node are not necessarily the transactions that have encountered problems or the transactions that the operations and maintenance personnel want to query. Therefore, although the target transaction information set can be displayed simultaneously and uniformly, the operations and maintenance personnel still need to find the transaction information of the problematic transactions or the transactions they want to query themselves. This will result in the operations and maintenance personnel still having low efficiency in analyzing transactions.

[0056] To further improve the efficiency of operations and maintenance personnel in analyzing transactions, this embodiment also adds target filtering transactions to the node filtering information. Target filtering transactions are those that operations and maintenance personnel have identified as problematic or those they wish to query. By adding these target filtering transactions to the node filtering information, unlike the scheme shown in Embodiment 1, when collecting the target transaction information set using the transaction information collection command generated based on the node filtering information, only the target filtering transactions involving each target filtering node are collected, rather than all transactions involving each target filtering node. This facilitates the accurate collection of transaction information for problematic or desired transactions during the collection phase. Thus, the target transaction information set subsequently displayed consists only of transaction information for transactions that operations and maintenance personnel deem problematic or desired, eliminating interference from irrelevant transaction information and improving the efficiency of transaction analysis.

[0057] S330. Display the target transaction information set in the form of a data table.

[0058] Example 4

[0059] This application provides a distributed database transaction information visualization method in Embodiment 4. This method optimizes the step in Embodiment 3, which involves "collecting transaction information under each target filtered transaction corresponding to the transaction information collection instruction based on the host agent to obtain a target transaction information set." It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes:

[0060] S410. Generate query conditions based on the acquired node filtering information, and query the component information corresponding to the query conditions from the preset metadata node; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0061] S421. Based on the query conditions and the component information, generate a transaction information collection instruction.

[0062] S422. Determine the host agent corresponding to the component information.

[0063] S423A. Based on the host agent, collect transaction information under each target filtered transaction corresponding to the transaction information collection instruction to obtain an initial transaction information set; the initial transaction information set includes an initial computing node transaction information set and an initial data node transaction information set.

[0064] It should be noted that the target filtering transaction corresponding to the transaction information collection instruction generally involves both computing nodes and data nodes. The computing nodes involved are denoted as target filtering computing nodes, and the data nodes involved are denoted as target filtering data nodes. When the host agent collects transaction information according to the transaction information collection instruction, it collects transaction information involving both the target filtering computing nodes and the target filtering data nodes. The collected transaction information involving each transaction of the target filtering computing nodes is denoted as the initial computing node transaction information set, and the collected transaction information involving each transaction of the target filtering data nodes is denoted as the initial data node transaction information set. The initial computing node transaction information set and the initial data node transaction information set together constitute the initial transaction information set.

[0065] S423B: Obtain the globally unique identifier of each transaction in the initial transaction information set.

[0066] It should be noted that the same target filtering transaction generally involves both compute nodes and data nodes. In this embodiment, the initial compute node transaction information set and the initial data node transaction information set are displayed on separate pages. Taking an initial compute node transaction information set as an example, in order to facilitate the analysis of the initial compute node transaction information by the operation and maintenance personnel, and to quickly find the initial data node transaction information corresponding to the same target filtering transaction, this embodiment can associate a set of corresponding initial compute node transaction information and initial data node transaction information through the globally unique identifier of the transaction corresponding to the same target filtering transaction.

[0067] S423C. Associate the transaction information of the transaction with the same globally unique identifier corresponding to the initial computing node transaction information set and the initial data node transaction information set to obtain the target transaction information set.

[0068] The initial compute node transaction information set and the initial data node transaction information set each contain a globally unique transaction identifier (transaction UUID). It should be noted that target filtering transactions involving both compute nodes and data nodes have the same globally unique transaction identifier in their corresponding initial compute node transaction information and initial data node transaction information. This globally unique transaction identifier allows association between the corresponding initial compute node transaction information and initial data node transaction information. Thus, on the interface displaying the initial compute node transaction information set, clicking this globally unique transaction identifier will directly jump to the corresponding initial data node transaction information, enabling operations and maintenance personnel to promptly obtain the necessary transaction information and improve their efficiency in analyzing transactions.

[0069] S430. Display the target transaction information set in the form of a data table.

[0070] Example 5

[0071] This application provides a distributed database transaction information visualization method in Embodiment 5. This method optimizes the "associating the transaction information of the initial computing node transaction information set with the transaction information of the same globally unique identifier corresponding to the initial data node transaction information set to obtain the target transaction information set" in Embodiment 4. It should be noted that for the parts not described in detail in this embodiment, please refer to the descriptions in other embodiments. The method includes:

[0072] S510. Generate query conditions based on the acquired node filtering information, and query the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0073] S521. Based on the query conditions and the component information, generate a transaction information collection instruction.

[0074] S522. Determine the host agent corresponding to the component information.

[0075] S523A. Based on the host agent, collect transaction information under each target filtered transaction corresponding to the transaction information collection instruction to obtain an initial transaction information set; the initial transaction information set includes an initial computing node transaction information set and an initial data node transaction information set.

[0076] S523B: Obtain the globally unique identifier of each transaction in the initial transaction information set.

[0077] S523C1. Determine the globally unique identifier of the transaction that is the same as that in the initial computing node transaction information set and the initial data node transaction information set, and obtain the target globally unique identifier.

[0078] For example, taking an initial computing node transaction information in the initial computing node transaction information set as an example, this initial computing node transaction information contains a corresponding globally unique transaction identifier (transaction UUID); taking an initial data node transaction information in the initial data node transaction information set as an example, this initial data node transaction information contains a corresponding globally unique transaction identifier (transaction UUID); if the above initial computing node transaction information and initial data node transaction information correspond to the same transaction, then the globally unique transaction identifiers (transaction UUIDs) corresponding to the two are the same.

[0079] Specifically, taking an initial computing node transaction as an example from the initial computing node transaction information set, first determine the globally unique identifier of the transaction in the initial computing node transaction information, and then determine whether there is an initial data node transaction information containing the globally unique identifier of the transaction in the initial data node transaction information. If it exists, record the globally unique identifier of the transaction as the target globally unique identifier.

[0080] S523C2. Determine the initial computing node transaction information corresponding to the target globally unique identifier in the initial computing node transaction information set, and obtain the computing node transaction information to be associated.

[0081] Among them, the transaction information of the computing node to be associated is the initial computing node transaction information corresponding to the target globally unique identifier in the initial computing node transaction information set.

[0082] S523C3. Determine the initial data node transaction information corresponding to the target globally unique identifier in the initial data node transaction information set, and obtain the data node transaction information to be associated.

[0083] Among them, the transaction information of the data node to be associated is the initial data node transaction information corresponding to the target globally unique identifier in the initial data node transaction information set.

[0084] S523C4. Associate the computing node to be associated with the data node to be associated in the initial computing node transaction information set to obtain the target transaction information set.

[0085] It should be noted that the transaction information of the computing nodes to be associated in the initial computing node transaction information set can be associated with the corresponding transaction information of the data nodes to be associated, and the initial transaction information set that completes the association between the transaction information of the computing nodes to be associated and the transaction information of the data nodes to be associated is denoted as the target transaction information set.

[0086] S530. Display the target transaction information set in the form of a data table.

[0087] It should be noted that the target transaction information set displays a globally unique identifier for the target in the initial computing node transaction information set. By clicking on this globally unique identifier, you can jump from the initial computing node transaction information set to the associated initial data node transaction information set.

[0088] Example 6

[0089] This application provides a distributed database transaction information visualization method in Embodiment Six, which supplements the method described in Embodiment One. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes:

[0090] S610. Generate query conditions based on the acquired node filtering information, and query component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node.

[0091] S620. Based on the query conditions and the component information, collect the transaction information under each target filter node corresponding to the node filter information to obtain the target transaction information set.

[0092] S630. Display the target transaction information set in the form of a data table.

[0093] S640. Perform transaction statistics on the target computing node transaction information set in the target transaction information set to obtain computing node transaction statistics results; the computing node transaction statistics results include at least: number of transactions, number of long transactions, maximum execution time of transactions, and number of components involved in transactions.

[0094] It should be noted that the initial transaction information set includes the initial compute node transaction information set and the initial data node transaction information set; the target transaction information set includes the target compute node transaction information set corresponding to the initial compute node transaction information set, and the target data node transaction information set corresponding to the initial data node transaction information set.

[0095] The target computing node transaction information set contains multiple target computing node transaction information sets. The number of transactions is the number of target computing node transaction information sets. The number of long transactions is the number of target computing node transaction information sets whose execution time exceeds a predetermined time threshold. The maximum execution time of a transaction is the maximum value of the execution time contained in each target computing node transaction information set. The number of components involved in a transaction is the number of components involved in the transaction corresponding to the target computing node transaction information set. Here, components are the computing nodes and data nodes involved in the transaction, and the number of computing nodes and data nodes are displayed separately.

[0096] Furthermore, the number of transactions, the number of long transactions, the maximum execution time of a transaction, and the number of components involved in a transaction are used as the transaction statistics results of the computing node corresponding to the transaction information set of the target computing node.

[0097] S650. Perform transaction statistics on the target data node transaction information set in the target transaction information set to obtain the data node transaction statistics results.

[0098] The steps for performing transaction statistics on the target data node transaction information set in the target transaction information set are the same as in S640, and will not be repeated here.

[0099] S660. Display the transaction statistics results of the computing nodes and the transaction statistics results of the data nodes on the target transaction information set.

[0100] In this embodiment, the transaction statistics results of compute nodes and data nodes are also displayed on the page showing the target transaction information set.

[0101] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0102] Example 7

[0103] Based on the same inventive concept, this embodiment also provides a distributed database transaction information visualization device for implementing the distributed database transaction information visualization method described above. The solution provided by this device is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more embodiments of the distributed database transaction information visualization device provided below can be found in the limitations of the distributed database transaction information visualization method described above, and will not be repeated here.

[0104] In this embodiment, as Figure 2 As shown, a distributed database transaction information visualization device is provided, comprising:

[0105] The information filtering module is used to generate query conditions based on the acquired node filtering information, and query component information corresponding to the query conditions from preset metadata nodes; wherein, the node filtering information includes target filtering clusters and target filtering nodes;

[0106] The information collection module is used to collect transaction information under each target filter node corresponding to the node filter information based on the query conditions and the component information, so as to obtain a target transaction information set;

[0107] The information display module is used to display the target transaction information set in the form of a data table.

[0108] Each module in the aforementioned distributed database transaction information visualization device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0109] It should be noted that this embodiment generates query conditions based on the acquired node filtering information, and queries the component information corresponding to the query conditions from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering nodes; based on the query conditions and the component information, transaction information under each of the target filtering nodes corresponding to the node filtering information is collected to obtain the target transaction information set; the target transaction information set is displayed in the form of a data table; through the above implementation, by using query conditions and component information, transaction information under each target filtering node under the target filtering cluster in the query conditions can be collected, and then the collected transaction information is uniformly displayed in the form of a data table. In this way, when a transaction has a problem, the operation and maintenance personnel can simultaneously view and analyze the transaction information under all nodes corresponding to the transaction displayed in the data table, thereby improving the efficiency of the operation and maintenance personnel in analyzing the cause of the transaction problem.

[0110] In an optional embodiment, in terms of collecting transaction information under each of the target filtering nodes corresponding to the node filtering information based on the query conditions and the component information to obtain a target transaction information set, the information collection module is specifically used for:

[0111] Based on the query conditions and the component information, a transaction information collection instruction is generated;

[0112] Determine the host agent corresponding to the component information;

[0113] Based on the host agent, transaction information under each target filtering node corresponding to the transaction information collection instruction is collected to obtain the target transaction information set.

[0114] In an optional embodiment, the node filtering information further includes: target filtering transactions; in terms of collecting transaction information under each target filtering node corresponding to the node filtering information based on the query conditions and the component information to obtain a target transaction information set, the information collection module is specifically used for:

[0115] Based on the query conditions and the component information, a transaction information collection instruction is generated;

[0116] Determine the host agent corresponding to the component information;

[0117] Based on the host agent, transaction information under each target filtered transaction corresponding to the transaction information collection instruction is collected to obtain the target transaction information set.

[0118] In an optional embodiment, regarding the collection of transaction information under each target filtered transaction corresponding to the transaction information collection instruction based on the host agent to obtain the target transaction information set, the information collection module is specifically used for:

[0119] Based on the host agent, transaction information under each target filtered transaction corresponding to the transaction information collection instruction is collected to obtain an initial transaction information set; the initial transaction information set includes an initial computing node transaction information set and an initial data node transaction information set.

[0120] Obtain the globally unique identifier of each transaction from the transaction information in the initial transaction information set;

[0121] The target transaction information set is obtained by associating the transaction information set of the initial computing node with the transaction information set of the initial data node with the transaction information set of the same globally unique identifier.

[0122] In an optional embodiment, regarding obtaining the target transaction information set by associating the transaction information of the initial computing node transaction information set with the transaction information of the same globally unique identifier corresponding to the initial data node transaction information set, the information acquisition module is specifically used for:

[0123] Determine the globally unique identifier of the transaction that is the same in the initial computing node transaction information set and the initial data node transaction information set to obtain the target globally unique identifier;

[0124] Determine the initial computing node transaction information corresponding to the target globally unique identifier in the initial computing node transaction information set to obtain the computing node transaction information to be associated.

[0125] Determine the initial data node transaction information corresponding to the target globally unique identifier in the initial data node transaction information set to obtain the data node transaction information to be associated.

[0126] The target transaction information set is obtained by associating the computing node to be associated with the data node to be associated in the initial computing node transaction information set.

[0127] In an optional embodiment, the distributed database transaction information visualization device further includes:

[0128] The computing node transaction statistics module is used to perform transaction statistics on the target computing node transaction information set in the target transaction information set to obtain computing node transaction statistics results; the computing node transaction statistics results include at least: the number of transactions, the number of long transactions, the maximum execution time of transactions, and the number of components involved in transactions.

[0129] The data node transaction statistics module is used to perform transaction statistics on the target data node transaction information set in the target transaction information set to obtain the data node transaction statistics results.

[0130] The statistical results display module is used to display the transaction statistical results of the computing node and the transaction statistical results of the data node on the target transaction information set.

[0131] Example 8

[0132] In this embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows. Figure 3 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a distributed database transaction information visualization method.

[0133] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the computer device to which the present disclosure is applied. A specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0134] Example 9

[0135] In this embodiment, a computer-readable storage medium is provided, such as... Figure 4As shown, a computer program is stored thereon, and when the computer program is executed by the processor, it implements the steps in the above-described method embodiments.

[0136] Example 10

[0137] In this embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0138] It should be noted that the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and it does not violate public order and good morals. Corresponding operation portals are provided for users to choose to authorize or refuse.

[0139] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this disclosure may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this disclosure may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0140] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0141] The embodiments described above are merely illustrative of several implementations of this disclosure, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent disclosure. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this disclosure, and these all fall within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the appended claims.

Claims

1. A method for visualizing distributed database transaction information, characterized in that, include: Based on the obtained node filtering information, query conditions are generated, and component information corresponding to the query conditions is queried from the preset metadata nodes; wherein, the node filtering information includes the target filtering cluster and the target filtering node; Based on the query conditions and the component information, transaction information under each target filter node corresponding to the node filter information is collected to obtain a target transaction information set; The target transaction information set is displayed in the form of a data table.

2. The method according to claim 1, characterized in that, Based on the query conditions and the component information, transaction information under each target filtering node corresponding to the node filtering information is collected to obtain a target transaction information set, including: Based on the query conditions and the component information, a transaction information collection instruction is generated; Determine the host agent corresponding to the component information; Based on the host agent, transaction information under each target filtering node corresponding to the transaction information collection instruction is collected to obtain the target transaction information set.

3. The method according to claim 1, characterized in that, The node filtering information also includes: target filtering transactions; Accordingly, based on the query conditions and the component information, the transaction information under each target filtering node corresponding to the node filtering information is collected to obtain the target transaction information set, including: Based on the query conditions and the component information, a transaction information collection instruction is generated; Determine the host agent corresponding to the component information; Based on the host agent, transaction information under each target filtered transaction corresponding to the transaction information collection instruction is collected to obtain the target transaction information set.

4. The method according to claim 3, characterized in that, Based on the host agent, the transaction information under each target filtered transaction corresponding to the transaction information collection instruction is collected to obtain the target transaction information set, including: Based on the host agent, transaction information under each target filtered transaction corresponding to the transaction information collection instruction is collected to obtain an initial transaction information set; the initial transaction information set includes an initial computing node transaction information set and an initial data node transaction information set. Obtain the globally unique identifier of each transaction from the transaction information in the initial transaction information set; The target transaction information set is obtained by associating the transaction information set of the initial computing node with the transaction information set of the initial data node with the transaction information set of the same globally unique identifier.

5. The method according to claim 4, characterized in that, The transaction information, which corresponds to the same globally unique identifier as the initial computing node transaction information set and the initial data node transaction information set, is used to obtain the target transaction information set, including: Determine the globally unique identifier of the transaction that is the same in the initial computing node transaction information set and the initial data node transaction information set to obtain the target globally unique identifier; Determine the initial computing node transaction information corresponding to the target globally unique identifier in the initial computing node transaction information set to obtain the computing node transaction information to be associated. Determine the initial data node transaction information corresponding to the target globally unique identifier in the initial data node transaction information set to obtain the data node transaction information to be associated. The target transaction information set is obtained by associating the computing node to be associated with the data node to be associated in the initial computing node transaction information set.

6. The method according to claim 1, characterized in that, Also includes: Perform transaction statistics on the target computing node transaction information set in the target transaction information set to obtain computing node transaction statistics results; The transaction statistics of the computing node include at least: the number of transactions, the number of long transactions, the maximum execution time of a transaction, and the number of components involved in a transaction; Perform transaction statistics on the target data node transaction information set in the target transaction information set to obtain the data node transaction statistics results; The transaction statistics results of the computing nodes and the transaction statistics results of the data nodes are displayed on the target transaction information set.

7. A distributed database transaction information visualization device, characterized in that, The device includes: The information filtering module is used to generate query conditions based on the acquired node filtering information, and query component information corresponding to the query conditions from preset metadata nodes; wherein, the node filtering information includes target filtering clusters and target filtering nodes; The information collection module is used to collect transaction information under each target filter node corresponding to the node filter information based on the query conditions and the component information, so as to obtain a target transaction information set; The information display module is used to display the target transaction information set in the form of a data table.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images