CN115809301B - Database processing method, device, electronic device and readable storage medium - Google Patents

Abstract

The embodiment of the application provides a database processing method, a device, electronic equipment and a readable storage medium, which belong to the technical field of computers, wherein the database processing method is applied to a distributed server, the distributed server is provided with a distributed database, the distributed server comprises a plurality of data sub-servers, and the method comprises the following steps: receiving a data processing request aiming at a distributed database, and determining lock resource parameters according to lock resource information associated with target data in the data processing request; acquiring target lock resources in a lock manager of each data sub-server according to the lock resource parameters; the target lock resource is a lock resource corresponding to the target data; and under the condition that the target lock resources in the lock managers of all the data sub-servers are successfully acquired, performing specified processing on the target data according to the operation indicated by the data processing request. The problem that the target data of each data sub-server cannot be synchronously processed is avoided, and the data consistency of the distributed database can be ensured.

Description

Database processing method, device, electronic device and readable storage medium

technical field

The present application belongs to the field of computer technology, and in particular relates to a database processing method, device, electronic equipment and readable storage medium.

Background technique

A distributed database is a database that stores data on different data sub-servers of a distributed server, and is logically a unified database. Clients can access the distributed database through a network connection and insert data in the distributed database. , update, delete and other operations.

In the prior art, when the data sub-server of the distributed server receives the data processing request sent by the client, it will directly find the target data requested by the client by querying the distributed database, and execute the processing flow in the data processing request to target data to operate.

After the target data in the distributed database is processed, it is necessary to synchronize the target data on different data sub-servers based on the lock resources corresponding to the target data in the data sub-servers. In the prior art, after data processing, there may be a problem that the target data on different data sub-servers cannot be synchronously processed, resulting in data inconsistency in the distributed database.

Contents of the invention

The present application provides a database processing method, device, electronic equipment, and readable storage medium, so as to solve the problem of data inconsistency in distributed databases caused by inability to synchronize data.

In order to solve the above-mentioned technical problems, the application is implemented as follows:

In a first aspect, the present application provides a method for processing a database, which is applied to a distributed server, the distributed server is provided with a distributed database, the distributed server includes a plurality of data sub-servers, and the method includes:

Receive a data processing request for the distributed database, and determine lock resource parameters according to lock resource information associated with target data in the data processing request; the target data is the data requested to be processed by the data processing request ;

Acquiring target lock resources in the lock managers of each of the data sub-servers according to the lock resource parameters; the target lock resources are lock resources corresponding to the target data;

In the case of successfully acquiring the target lock resources in the lock managers of all the data sub-servers, perform specified processing on the target data according to the operation indicated by the data processing request.

Optionally, the data processing request includes a data processing code; receiving the data processing request for the distributed database, and determining lock resource parameters according to the lock resource information associated with the target data in the data processing request ,include:

receiving a data processing request for the distributed database through the target data sub-server in the distributed server;

performing aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code;

Determine lock resource parameters according to lock resource information associated with the target data in the lock resource subcode.

Optionally, the acquiring target lock resources in the lock managers of each of the data sub-servers according to the lock resource parameters includes:

Acquiring the target lock resource in the lock manager of the target data sub-server according to the lock resource parameter;

Synchronize the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server based on the preset registration nodes corresponding to the data sub-servers in the coordination service component;

For any of the other data sub-servers, the other data sub-server obtains the target lock resource in the lock manager of the other data sub-server according to the lock resource parameter.

Optionally, the registration node corresponding to each of the data sub-servers in the preset-based coordination service component synchronizes the lock resource parameters to all of the multiple data sub-servers except the target data sub-server Other data subservers, including:

Establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component;

sending the lock resource parameter to the coordination service component through the first connection based on the target data sub-server;

For any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, the lock resource parameter is sent to the other data sub-servers.

Optionally, before acquiring the target lock resource in the lock manager of each data sub-server according to the lock resource parameter, the method further includes:

In response to the data processing request, establishing a second connection between the client and the distributed database through the target data sub-server; the client is a device that sends the data processing request to the target data sub-server;

The specified processing of the target data according to the operation indicated by the data processing request includes:

Execute the data processing code based on the target data sub-server to obtain data processing information from the client through the second connection, and process the target data in the distributed database according to the data processing information Perform specified processing; the data processing code is used to implement the operation indicated by the data processing request.

Optionally, the method also includes:

If the target lock resources in the lock managers of all the data sub-servers are not successfully obtained, the second connection is disconnected, so that other clients can establish a connection with the distributed database and update the distributed database. Data in the database is processed.

Optionally, the distributed server also includes a backup sub-server, and the method also includes:

When the timing parameters in the backup sub-server meet the preset time requirements, obtain the operation logs of each of the data sub-servers through the backup sub-server, and store the obtained operation logs in the backup sub-server ;

If there is an error log in the operation log stored by the backup sub-server, the data in the data sub-server corresponding to the error log is corrected based on the backup sub-server.

Optionally, the error correction of the data in the data sub-server corresponding to the error log based on the backup sub-server includes:

Based on the backup sub-server, determine error data according to the error log, and determine the data sub-server storing the error data as the first data sub-server;

Selecting a data sub-server storing correct data corresponding to the erroneous data as a second data sub-server according to the erroneous data;

Based on the backup sub-server, acquire the correct data in the second data sub-server, and replace the erroneous data in the first data sub-server with the correct data.

In a second aspect, the present application provides a database processing device, which is applied to a distributed server, the distributed server is provided with a distributed database, the distributed server includes a plurality of data sub-servers, and the device includes:

A determining module, configured to receive a data processing request for the distributed database, and determine lock resource parameters according to lock resource information associated with target data in the data processing request; the target data is the data processing request the data requested to be processed;

An acquisition module, configured to acquire a target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameter; the target lock resource is a lock resource corresponding to the target data;

The processing module is configured to perform specified processing on the target data according to the operation indicated by the data processing request when the target lock resources in the lock managers of all the data sub-servers are successfully acquired.

Optionally, the data processing request includes a data processing code; the determining module is specifically used for:

receiving a data processing request for the distributed database through the target data sub-server in the distributed server;

performing aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code;

Determine lock resource parameters according to lock resource information associated with the target data in the lock resource subcode.

Optionally, the acquiring module is specifically used for:

Acquiring the target lock resource in the lock manager of the target data sub-server according to the lock resource parameter;

Synchronize the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server based on the preset registration nodes corresponding to the data sub-servers in the coordination service component;

For any of the other data sub-servers, the other data sub-server obtains the target lock resource in the lock manager of the other data sub-server according to the lock resource parameter.

Optionally, the acquisition module is also specifically used for:

Establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component;

sending the lock resource parameter to the coordination service component through the first connection based on the target data sub-server;

For any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, the lock resource parameter is sent to the other data sub-servers.

Optionally, the device also includes:

The connection module is used for the acquisition module to establish through the target data sub-server in response to the data processing request before acquiring the target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameters. A second connection between the client and the distributed database; the client is a device that sends the data processing request to the target data sub-server;

The processing module is specifically configured to: execute the data processing code based on the target data sub-server, so as to obtain data processing information from the client through the second connection, and process the distribution according to the data processing information. The specified processing is performed on the target data in the database; the data processing code is used to implement the operation indicated by the data processing request.

Optionally, the device also includes:

A disconnection module, configured to disconnect the second connection when the target lock resources in the lock managers of all the data sub-servers are not successfully obtained, so that other clients can establish with the distributed database Connect and process the data in the distributed database.

Optionally, the distributed server also includes a backup sub-server, and the device also includes:

A storage module, configured to obtain the operation logs of each of the data sub-servers through the backup sub-server when the timing parameters in the backup sub-server meet the preset time requirements, and store the obtained operation logs in the in the backup subserver;

The error correction module is configured to correct the data in the data sub-server corresponding to the error log based on the backup sub-server when there is an error log in the operation log stored in the backup sub-server.

Optionally, the error correction module is specifically used for:

Based on the backup sub-server, determine error data according to the error log, and determine the data sub-server storing the error data as the first data sub-server;

Selecting a data sub-server storing correct data corresponding to the erroneous data as a second data sub-server according to the erroneous data;

Based on the backup sub-server, acquire the correct data in the second data sub-server, and replace the erroneous data in the first data sub-server with the correct data.

In a third aspect, the present application provides an electronic device, including: a processor, a memory, and a computer program stored on the memory and operable on the processor, and the above-mentioned database is realized when the processor executes the program Approach.

In a fourth aspect, the present application provides a readable storage medium. When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device can execute the above database processing method.

In the embodiment of the present application, by receiving a data processing request for a distributed database, and according to the lock resource information associated with the target data in the data processing request, the lock resource parameters are determined; the target data is the data requested to be processed by the data processing request ;According to the lock resource parameters, obtain the target lock resource in the lock manager of each data sub-server; the target lock resource is the lock resource corresponding to the target data; successfully obtain the target lock resource in the lock manager of all data sub-servers In the case of , the specified processing is performed on the target data according to the operation indicated by the data processing request. For distributed databases, due to network errors or system errors, there may be differences in the lock resources of different data sub-servers. For example, the lock resources in the lock manager of some data sub-servers include target lock resources, while the lock management of some data sub-servers The lock resources in the server do not include the target lock resources. Because when synchronizing the target data on different data sub-servers, the target lock resources corresponding to the target data on each data sub-server need to be used. The lock resources in the lock manager of some data sub-servers include target lock resources. However, if the lock resource in the lock manager of some data sub-servers does not include the target lock resource, it will not be possible to synchronize the target data on different data sub-servers, resulting in data inconsistency in the distributed database. . In the embodiment of the present application, only when the target lock resources in the lock managers of all data sub-servers are successfully acquired, the target data is specified and processed according to the operation indicated by the data processing request. In this way, it can avoid the difference in lock resources of different data sub-servers during subsequent synchronization processing, that is, there are target lock resources in the lock managers of some data sub-servers, while there are no target lock resources in the lock managers of some data sub-servers. Lock resources, resulting in the inability to synchronize target data on different data sub-servers, thereby ensuring data consistency in distributed databases.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a flow chart of the steps of a database processing method provided in the embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario of a database processing method provided in an embodiment of the present application;

Fig. 3 is a flow chart of steps of another database processing method provided by the embodiment of the present application;

FIG. 4 is a structural diagram of a database processing device provided in an embodiment of the present application;

FIG. 5 is a structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

Fig. 1 is a flow chart of the steps of a database processing method provided by the embodiment of the present application. As shown in Fig. 1, the method is applied to a distributed server, and a distributed database is arranged on the distributed server, and the distributed server comprising a plurality of data sub-servers, the method comprising:

Step 101, receiving a data processing request for the distributed database, and determining lock resource parameters according to the lock resource information associated with the target data in the data processing request; the target data is requested by the data processing request processed data.

In this embodiment of the present application, a distributed server refers to a server device cluster including multiple sub-servers distributed in different geographic locations. The data sub-server refers to a sub-server for storing data of the distributed database among the multiple sub-servers included in the distributed server. The data processing request may be a network data packet sent by a computer device accessing the distributed database, and the network data packet contains lock resource information associated with the target data. Among them, the computer equipment that accesses the distributed database can be a client or a proxy server that forwards the data processing request sent by the client. The proxy server is connected to the distributed server and acts as an intermediate layer between the client and the distributed server for receiving and forwarding The data processing request sent by the client to the distributed server.

In this embodiment of the application, the lock resource parameter can be, for example, the database primary key corresponding to the lock resource in the distributed database, the library name and table name of the database, etc., and the lock resource information can include the database primary key related to the lock resource corresponding to the target data, the database library The information such as name and table name is just an example here, and this embodiment of the present application does not limit it. Among them, the primary key of the database refers to a column or a combination of multiple columns corresponding to each row of the data table in the distributed database, and the library name and table name of the database refer to the identification of each sub-database of the distributed database and The ID of the data table.

In this embodiment of the present application, the distributed server may receive a data processing request sent by a computer device such as a client or a proxy server to one of the data sub-servers of the distributed server. Among them, the data processing request can be generated by the computer device based on its own processing requirements for the data in the distributed database. For example, the computer device needs to query, update, and delete certain data in the distributed Insert data into the database, etc., and generate a data processing request according to the data to be processed, the data processing operations to be performed, and the relevant information of the lock resource corresponding to the data in the distributed database. This is only for illustration, and this embodiment of the present application does not limit it.

In this embodiment of the application, after the distributed server receives the data processing request, it can analyze the network data packet corresponding to the data processing request, and obtain a part of data related to the lock resource in the network data packet, that is, the data associated with the target data. Lock resource information, for example, information such as database primary key, database library name and table name, and then use the actual value corresponding to the lock resource information as the lock resource parameter.

Step 102, according to the lock resource parameters, acquire target lock resources in the lock managers of each of the data sub-servers; the target lock resources are lock resources corresponding to the target data.

In the embodiment of this application, all the lock resources corresponding to all the data in the distributed database can be integrated into a whole and managed in the distributed lock manager. The image of the distributed lock manager is stored on the subservers, and the image is used as the lock manager of the data subserver. For any data sub-server, the program code corresponding to the lock manager can be stored in the memory of the data sub-server, and the data corresponding to the lock manager in the memory can be read through the central processing unit (Central Processing Unit, CPU) of the data sub-server. The program code calls the lock manager.

In this embodiment of the application, for the lock manager of any data sub-server, the lock resource matching the lock resource parameter in the lock manager can be searched according to the lock resource parameter, and the lock whose actual parameter is consistent with the lock resource parameter can be obtained. resource, get the target lock resource. Specifically, you can use the keyword in the lock resource parameter to find the lock resource whose target keyword matches the searched keyword in the lock manager, and compare whether the actual value of the lock resource is consistent with the value corresponding to the lock resource parameter. If the target key If the word matches the search keyword and the values are consistent, the found lock resource is the target lock resource corresponding to the target data.

Step 103, in the case of successfully acquiring the target lock resources in the lock managers of all the data sub-servers, perform specified processing on the target data according to the operation indicated by the data processing request.

In the embodiment of the present application, the lock manager is an image of the distributed lock manager stored in any data sub-server, and the lock manager includes lock resources corresponding to all data of the distributed database. For any target data, the lock manager of each data sub-server has a target lock resource corresponding to the target data, even if the target data is not stored in all data sub-servers, only one or more of them on the server. Therefore, the successful acquisition of the target lock resources in the lock managers of all data sub-servers means that all lock resources of all data sub-servers storing target data have been obtained, ensuring that the target locks corresponding to the target data on each data sub-server Resource synchronization is acquired.

In the embodiment of this application, if the target lock resources in the lock managers of all data sub-servers are successfully acquired, the operation indicated by the data processing request can be executed by the data sub-servers storing the target data in the distributed server Corresponding insert, update, delete, etc. codes respectively perform specified processing on the data in the sub-databases of the distributed database set on the data sub-servers storing the target data, such as insert, update, delete, etc., and complete the data processing request operate.

Specifically, the data processing operation code can be run based on the data sub-server receiving the data processing request in the distributed server, and send a data processing instruction to the data sub-server storing the target data through the communication network of each data sub-server in the distributed server , to instruct each data sub-server storing the target data to perform specified processing such as insertion, update, and deletion on the target data in their respective sub-databases according to the data processing instructions, so that the target data in the distributed database is processed synchronously, which can avoid any A problem that the target data on the data sub-server storing the target data is inconsistent with the processed target data on other data sub-servers storing the target data. For example, if the data processing request indicates to update the quantity of a certain device in the device ledger stored in the distributed database, the distributed server can run the database language (Structured Query) corresponding to the data update operation through the data sub-server receiving the data processing request. Language, SQL), at the same time, update the value of the number of devices on the data sub-server that stores a certain number of devices, or update the value of the number of devices on the data sub-server that stores a certain number of devices in turn, here is just an example It should be noted that this embodiment of the present application does not limit this.

In the embodiment of the present application, by receiving a data processing request for a distributed database, and according to the lock resource information associated with the target data in the data processing request, the lock resource parameters are determined; the target data is the data requested to be processed by the data processing request ;According to the lock resource parameters, obtain the target lock resource in the lock manager of each data sub-server; the target lock resource is the lock resource corresponding to the target data; successfully obtain the target lock resource in the lock manager of all data sub-servers In the case of , the specified processing is performed on the target data according to the operation indicated by the data processing request. For distributed databases, due to network errors or system errors, there may be differences in the lock resources of different data sub-servers. For example, the lock resources in the lock manager of some data sub-servers include target lock resources, while the lock management of some data sub-servers The lock resources in the server do not include the target lock resources. Because when synchronizing the target data on different data sub-servers, the target lock resources corresponding to the target data on each data sub-server need to be used. The lock resources in the lock manager of some data sub-servers include target lock resources. However, if the lock resource in the lock manager of some data sub-servers does not include the target lock resource, it will not be possible to synchronize the target data on different data sub-servers, resulting in data inconsistency in the distributed database. . In the embodiment of the present application, only when the target lock resources in the lock managers of all data sub-servers are successfully obtained, the target data is specified and processed according to the operation indicated by the data processing request. In this way, it can avoid the difference in the lock resources of different data sub-servers during subsequent synchronization processing, that is, some data sub-servers have target lock resources in the lock manager, while some data sub-servers do not have target lock resources in the lock manager. Lock resources, resulting in the inability to synchronize target data on different data sub-servers, thereby ensuring data consistency in distributed databases.

Optionally, the data processing request includes a data processing code; step 101 may include the following steps:

Step 1011, receiving a data processing request for the distributed database through the target data sub-server in the distributed server.

In the embodiment of the present application, the distributed server may include multiple data sub-servers distributed in different geographical locations, and the distributed server may receive the data processing request for the distributed database sent by the computer device through each included data sub-server. Wherein, the computer device can directly send the data processing request to the data sub-server of the distributed server, and the data sub-server receiving the data processing request is the target data sub-server. The distributed server can receive the data processing request for the distributed database sent by the computer device through the target data sub-server, then the target data sub-server becomes the connection node for the computer device to access the distributed database this time, and the distributed server can use this connection node to Distributed databases set on each data sub-server for access control.

Step 1012, perform aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code.

In the embodiment of the present application, the data processing code may be a database programming language related to data processing operations in the network data packet corresponding to the data processing request, and the data processing code includes the lock resource acquisition part code corresponding to the target data and the target data processing part code. Wherein, the code of the target data processing part may be, for example, SQL statements of insert, update, and delete corresponding to insert, update, and delete operations. The lock resource acquisition part code is the lock resource subcode, which may include lock resource information, lock conflict, lock waiting processing logic, etc.

In the embodiment of the present application, section processing refers to cutting the packaged code, and adding some new code to the original code to enhance the original code. The target data sub-server can cut the data processing code by running the aspect program language in the target data sub-server, add separation code in the data processing code, and find the lock resource sub-code in the data processing code through the separation code, and from The lock resource subcode is extracted from the data processing code, thereby realizing the operation of separating the lock resource subcode from the data processing code. Specifically, the aspect module of the open source application tool on the Java development platform can be used to perform aspect processing on the data processing code, so as to separate the lock resource subcode from the data processing code. This is only for illustration, and this embodiment of the present application does not limit it.

Step 1013: Determine lock resource parameters according to the lock resource information associated with the target data in the lock resource subcode.

In the embodiment of this application, the target data sub-server can analyze the lock resource sub-code, and obtain the code statement related to the lock resource corresponding to the acquired target data in the lock resource sub-code, and the lock resource information contained in the code statement is related to the target The lock resource information associated with the data, such as database primary key, database name and table name, etc., and then, the actual value corresponding to the lock resource information is determined as the lock resource parameter.

It should be noted that the lock resources corresponding to distributed databases have different lock levels, also known as different lock granularities. The data processing efficiency of distributed databases is different when different lock granularities are acquired. After acquiring lock resources with smaller granularity , the query rate per second (QueriesPer Second, QPS) and the number of transactions per second (TransactionsPerSecond, TPS) corresponding to each data sub-server in the distributed server where the distributed database is located are significantly improved, thereby improving the data processing efficiency of the distributed database.

In the embodiment of this application, by performing face-to-face processing on the data processing code and separating the lock resource subcode from the data processing code, the lock resource information associated with the target data in the lock resource subcode can be used to determine the lock resource information of a smaller granularity. Lock resource parameters corresponding to the lock resource.

In the embodiment of the present application, the data processing request for the distributed database is received through the target data sub-server in the distributed server; based on the target data sub-server, the data processing code is aspect-processed to separate the lock from the data processing code. The resource subcode; determine the lock resource parameters according to the lock resource information associated with the target data in the lock resource subcode. In this way, the data processing request for the distributed database can be conveniently received based on the target data sub-server, and the response speed of the distributed database can be improved, and since the lock resource subcode is separated after the data processing code is cut, the lock resource subcode The lock resource information associated with the target data is more detailed, so that the lock resource granularity corresponding to the lock resource parameters determined according to the lock resource information is smaller, and further, the target lock resource obtained by the distributed server is more accurate, thereby improving the distributed The server's lock resource acquisition efficiency.

Optionally, step 102 may include the following steps:

Step 1021, according to the lock resource parameter, acquire the target lock resource in the lock manager of the target data sub-server.

In this embodiment of the application, the distributed server can receive the data processing request for the distributed database through the target data sub-server, and directly process the data processing code in the target data sub-server to separate the lock resource sub-code, and The lock resource information associated with the target data in the resource subcode determines the lock resource parameters, so that the target data subserver itself obtains the lock resource parameters. The target data sub-server can directly call the lock manager according to the lock resource parameters obtained by itself and acquire the target lock resource in the lock manager. For the specific acquisition process, refer to the related description in step 102, which will not be repeated here.

Step 1022, based on the registration node corresponding to each of the data sub-servers in the preset coordination service component, synchronize the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server server.

In the embodiment of this application, the coordination service component refers to the software that provides consistent coordination services for distributed databases. The coordination service component encapsulates the coordination service into a simple interface and provides it to users. Each data sub-server in the distributed server is registered, so that each data sub-server in the distributed server can be coordinated and managed through the coordination service component. The registration node refers to the dedicated node created when each data sub-server is registered in the coordination service component. The dedicated node stores the Internet protocol address (Internet Protocol Address, IP address), port, calling method (protocol, sequence) corresponding to the data sub-server way) etc.

In the embodiment of this application, the target data sub-server can establish a connection between the target data sub-server and the coordination service component through the corresponding registration node of the target data sub-server in the coordination service component, and then through the established connection, the target data sub-server The lock resource parameters are sent to the coordination service component, and the coordination service component establishes connections with other data sub-servers through their corresponding registration nodes, and then sends the lock resource parameters to other data sub-servers to realize the synchronization of the lock resource parameters to the Data subservers other than the target data subserver among multiple data subservers.

Step 1023, for any of the other data sub-servers, obtain the target lock resources in the lock manager of the other data sub-servers through the other data sub-servers according to the lock resource parameters.

In the embodiment of this application, for any other data sub-server, the data sub-server can search for the lock resource matching the lock resource parameter in the lock manager of the data sub-server according to the lock resource parameter, and obtain the actual parameter The lock resource whose parameter is consistent with the lock resource obtains the target lock resource in the lock manager of the data subserver. For the specific search and acquisition process, reference may be made to the relevant description of step 102, which will not be repeated here.

In the embodiment of the present application, by obtaining the target lock resource in the lock manager of the target data sub-server according to the lock resource parameter; based on the registration node corresponding to each data sub-server in the preset coordination service component, the lock resource parameter is synchronized To other data sub-servers in multiple data sub-servers except the target data sub-server; for any other data sub-server, obtain the target lock resource in the lock manager of other data sub-servers through other data sub-servers according to the lock resource parameters . In this way, it is convenient to directly obtain the target lock resource in the lock manager of the target data sub-server according to the lock resource parameters in the target data sub-server, and by coordinating the registration nodes corresponding to each data sub-server in the service component, it is convenient to transfer the lock to The resource parameters are synchronized to other data sub-servers, so that other data sub-servers can also obtain the target lock resources in their own lock manager according to the lock resource parameters, and the operation of synchronizing lock resource parameters through the coordination service component can speed up the acquisition of each data sub-server The speed of the target lock resource in the lock manager, thereby improving the acquisition efficiency of the target lock resource.

Optionally, step 1022 may include the following steps:

Step 1022a, establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component.

In the embodiment of the present application, the registration node corresponding to the target data sub-server is a dedicated node created when the target data sub-server is registered in the coordination service component, and the dedicated node stores the corresponding Internet Protocol Address (Internet Protocol Address, IP address), port, calling method (protocol, serialization method), etc. The target data sub-server can call the target port corresponding to the target data sub-server according to the calling method stored in the corresponding registration node, so as to establish a connection between the target data sub-server and the corresponding registration node in the coordination service component through the target port, and Use the established connection as the first connection.

Step 1022b, based on the target data sub-server, send the lock resource parameter to the coordination service component through the first connection.

In this embodiment of the application, the target data sub-server may send the lock resource parameters in the target data sub-server to the target data sub-server in the coordination service component based on the first connection between the target data sub-server and the corresponding registration node in the coordination service component. The target port corresponding to the server, and then the coordination service component receives the lock resource parameter through the target port, so that the lock resource parameter is sent to the coordination service component through the first connection.

Step 1022c, for any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, send the lock resource parameter to the other data sub-servers.

In this embodiment of the application, referring to the relevant description in step 1022, for any other data sub-server, the coordination service component is set with a dedicated node created when the data sub-server is registered, that is, a registration node, and the registration node stores the data sub-server The corresponding Internet protocol address (Internet Protocol Address, IP address), port, calling method (protocol, serialization method), etc. of the server. The target data sub-server can call the target port corresponding to the data sub-server according to the call method stored in the registration node corresponding to the data sub-server, and establish the connection between the data sub-server and the corresponding registration node in the coordination service component through the target port. connection, and then send the lock resource parameters from the coordination service component to the data sub-server through the established connection, so as to send the lock resource parameters to other data sub-servers based on the registration node corresponding to other data sub-servers in the coordination service component.

In the embodiment of this application, by establishing the first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component; based on the target data sub-server, the lock resource parameter is sent to the coordination Service component; for any other data sub-server, based on the registration node corresponding to other data sub-server in the coordination service component, send the lock resource parameter to other data sub-server. In this way, through the first connection between the target data sub-server and the corresponding registration node in the coordination service component, the lock resource parameters can be easily obtained from the target data sub-server, and based on the corresponding registration nodes of other data sub-servers in the coordination service component, Conveniently synchronize the lock resource parameters to other data sub-servers, thereby improving the synchronization efficiency of lock resource parameters by coordinating the registration nodes corresponding to each data sub-server in the service component.

Optionally, before step 102, the method further includes:

Step 201, in response to the data processing request, establish a second connection between the client and the distributed database through the target data sub-server; the client sends the data processing request to the target data sub-server device of.

In the embodiment of this application, the management tool corresponding to the distributed database can be pre-installed in the client, and the IP address of each data sub-server of the distributed server is stored in the management tool. The data sub-server sends a data processing request. After receiving the data processing request, the target data sub-server first establishes a communication connection between the client and the target data sub-server in response to the data processing request, and then queries the distribution of the user name and password sent by the client in the network data packet corresponding to the data processing request. If the verification is passed, the target data sub-server will connect to the distributed database through the communication network with other data sub-servers in the distributed server, so as to realize the connection between the client and the distributed database through the target data sub-server, and will establish connection as the second connection.

Optionally, step 103 may include the following steps:

Step 1031: Execute the data processing code based on the target data sub-server, so as to obtain data processing information from the client through the second connection, and process all data in the distributed database according to the data processing information The target data is specified for processing; the data processing code is used to implement the operation indicated by the data processing request.

In this embodiment of the present application, the data processing information may be operation information and data information required for specified processing of target data. For example, the data processing request indicates to perform specified processing such as insertion, update, and deletion on the target data, and the data processing information may include the data that needs to be inserted into the distributed database, the update data corresponding to the update operation on the target data, or the distribution that needs to be deleted. Information about the target data in the database, etc. This is only for illustration, and this embodiment of the present application does not limit it.

In the embodiment of this application, the data processing code can be run based on the target data sub-server, first send an information acquisition instruction to the client, instruct the client to send data processing information, and then send the data to the storage through the communication network of each data sub-server in the distributed server. A data sub-server with target data sends a data processing instruction, wherein the data processing instruction may include data processing information. Each data sub-server storing the target data receives the data processing instruction, and in response to the data processing instruction, performs specified processing on the target data in the sub-databases set on the data sub-server according to the operation information and data information in the data processing information .

In this embodiment of the application, by responding to the data processing request, the second connection between the client and the distributed database is established through the target data sub-server; the client is a device that sends a data processing request to the target data sub-server; based on the target data sub-server The server executes the data processing code to obtain data processing information from the client through the second connection, and performs specified processing on the target data in the distributed database according to the data processing information; the data processing code is used to implement the operation indicated by the data processing request. In this way, the data processing information can be conveniently obtained based on the second connection between the client and the distributed database based on the target data sub-server. Further, the processing speed of the target data is accelerated by executing the data processing code through the target data sub-server, thereby improving the distributed database. The data processing efficiency of the database.

Optionally, the method also includes:

Step 301, if the target lock resources in the lock managers of all the data sub-servers are not successfully acquired, disconnect the second connection so that other clients can establish connections with the distributed database and The data in the distributed database is processed.

In the embodiment of this application, if the target lock resources in the lock managers of all data sub-servers are not successfully acquired, the reasons may include: first, the target lock resources corresponding to the target data have been sent by other clients for data processing requests Occupied. At this time, the target data is being processed by the operation indicated by the data processing request sent by other clients, so the target lock resource cannot be acquired. Second, due to a network error or system error, the lock resource corresponding to the target data on one or more data sub-servers is abnormal, that is, it is inconsistent with the target lock resource in the lock manager of other normal data sub-servers, so the lock resource exception The target lock resource does not exist in the lock manager of the data sub-server, and the target lock resource in the lock manager of the data sub-server where the lock resource is abnormal cannot be obtained.

In the embodiment of this application, in order to ensure that there is no logical conflict in the data processing process and the data consistency of the distributed database, only when the target lock resources in the lock managers of all data sub-servers are successfully obtained, the data processing The operation indicated by the request performs the specified processing on the target data. However, if the target lock resource in the lock manager of all data sub-servers is not successfully obtained, the second connection can be disconnected by the target data sub-server, and wait for a certain period of time according to the processing logic of the lock waiting part in the data processing code Then re-establish the second connection between the client and the distributed database through the target data sub-server, so as to perform specified processing on the target data according to the operation indicated by the data processing request. After the second connection is disconnected, the distributed server can receive data processing requests from other clients for distributed data, and establish connections between other clients and the distributed database to process data in the distributed database.

In this embodiment of the application, by disconnecting the second connection when the target lock resources in the lock managers of all data sub-servers are not successfully obtained, it is convenient for other clients to establish a connection with the distributed database, and to The data in the distributed database is processed, thus the rationality and practicability of the database processing method of the present application are mentioned.

Optionally, the distributed server also includes a backup sub-server, and the method also includes:

Step 401, when the timing parameters in the backup sub-server meet the preset time requirements, obtain the operation logs of each of the data sub-servers through the backup sub-server, and store the obtained operation logs in the backup sub-server in the subserver.

In the embodiment of the present application, the backup sub-server is used to regularly back up the operation logs corresponding to each data sub-server, and perform data recovery tasks according to the backup operation logs, so as to correct the error data in the distributed database. The operation log of the data sub-server records the server identifier of the data sub-server, such as the IP address, and the operation record of inserting, updating or deleting certain data. The timing parameter may be a time variable that is regularly reset to zero, and is used to time the periodic backup task of the backup sub-server. The preset time requirement may be determined according to the time period requirement of the regular backup task of the backup sub-server, for example, the preset time requirement may be one day, one week or one month. This is only for illustration, and this embodiment of the present application does not limit it.

In the embodiment of this application, the fact that the timing parameters in the backup sub-server meet the preset time requirements means that the current parameter value of the timing parameters is consistent with the preset value required by the preset time, indicating that the current moment meets the regular backup of the backup sub-server The trigger condition of the task. In this case, the timing parameter is automatically triggered to be reset to zero, and the distributed server scans each data sub-server through the backup sub-server and obtains the operation log of each data sub-server, and stores the obtained operation log in the backup sub-server. The specified memory area in the server to regularly back up the operation logs corresponding to each data sub-server.

Step 402, if there is an error log in the operation log stored in the backup sub-server, correct the data in the data sub-server corresponding to the error log based on the backup sub-server.

In this embodiment of the present application, the error log may be an operation log in which the recorded operation record indicates that data of the data sub-server corresponding to the error log is inconsistent with data of other data sub-servers. Wherein, the operation record that causes data inconsistency may include: first, the target data on the data sub-server corresponding to the error log is inconsistent with the target data on other data sub-servers after modification. Or, secondly, the operation logs of other data sub-servers that store the target data record operations on the target data, but there is no corresponding operation record in the error log, that is, the target data on the data sub-server corresponding to the error log is not synchronized be processed.

In the embodiment of the present application, when there is an error log in the operation log stored by the backup sub-server, the data sub-server corresponding to the error log can be found based on the server identification of the data sub-server recorded by the backup sub-server according to the error log. For the first In this case, undo the operation on the target data on the data sub-server, and restore the data before data processing, so that the target data on the data sub-server corresponding to the error log is consistent with the target data on other data sub-servers, that is, data recovery. For the second case, according to the operations on the target data recorded in the operation logs of other data sub-servers that store the target data, the target data on the data sub-server corresponding to the error log is synchronously processed, so that the data sub-server corresponding to the error log The target data on the server is consistent with the target data on other data sub-servers, that is, data synchronization. Through the process of data recovery or data synchronization, the error correction of the data in the data sub-server corresponding to the error log is implemented based on the backup sub-server.

In this embodiment of the application, when the timing parameters in the backup sub-server meet the preset time requirements, the backup sub-server obtains the operation logs of each data sub-server, and stores the obtained operation logs in the backup sub-server ; If there is an error log in the operation log stored in the backup sub-server, correct the data in the data sub-server corresponding to the error log based on the backup sub-server. In this way, according to the timing parameters and preset time requirements, the operation logs of each data sub-server can be easily backed up through the backup sub-service, and the data in the data sub-server corresponding to the error log can be corrected through the backup sub-server, which can Reduce erroneous data in distributed databases, thereby improving data consistency in distributed databases.

Optionally, step 402 may include the following steps:

Step 4021, based on the backup sub-server, determine error data according to the error log, and determine the data sub-server storing the error data as the first data sub-server.

In the embodiment of the present application, the error log can be analyzed based on the backup sub-server, and it is determined that when the data sub-server corresponding to the error log is inconsistent with the target data of other data sub-servers in the error log, the wrong operation record in the error log or Missing action record. Wherein, for the wrong operation record or the missing operation record, reference may be made to the relevant description in step 402, which will not be repeated here. Then, according to the erroneous operation records or missing operation records in the error log, the data inconsistent with the data stored on other data sub-servers is found, and the found data is determined as erroneous data. The data sub-server storing the erroneous data can be found according to the server identifier of the data sub-server recorded in the error log, and the found data sub-server is determined as the first data sub-server.

Step 4022, according to the erroneous data, select a data sub-server storing the correct data corresponding to the erroneous data as the second data sub-server.

In this embodiment of the application, the error data refers to the data stored in the first data sub-server corresponding to the wrong operation record or missing operation record in the error log, and the wrong operation record or missing operation corresponding to the error data can be Record and determine the operation log corresponding to the correct operation record, and determine the data sub-server storing the correct data corresponding to the error data according to the server identification recorded in the correct operation log. One of the data sub-servers with correct data can be selected as the second data sub-server, or the data sub-server whose address is closest to the first data sub-server among the data sub-servers with correct data can be selected, As the second data sub-server, this embodiment of the present application does not limit it.

Step 4023, based on the backup sub-server, obtain the correct data in the second data sub-server, and replace the wrong data in the first data sub-server with the correct data.

In the embodiment of this application, the communication network of each data sub-server in the distributed server can be connected based on the backup sub-server, and the correct data can be obtained from the sub-database set on the second data sub-server through the communication network and sent to the first data sub-server. server, then replace the wrong data in the sub-database set on the first data sub-server with correct data.

Optionally, a recovery queue can be set in the backup sub-server, and when the backup sub-server finds that there is an error log in the stored operation log, it can store the error log in the recovery queue. The distributed server takes out the error log from the recovery queue sequentially through the recovery thread, and analyzes and processes the error log, so as to correct the error data in the distributed database according to the error log.

In the embodiment of the present application, the error data is determined according to the error log based on the backup sub-server, and the data sub-server storing the error data is determined as the first data sub-server; according to the error data, the correct data corresponding to the error data is selected One of the data sub-servers is used as the second data sub-server; based on the backup sub-server, the correct data in the second data sub-server is obtained, and the wrong data in the first data sub-server is replaced with correct data. In this way, error correction can be conveniently performed on the data in the data sub-server storing erroneous data based on the backup sub-server, thereby improving the efficiency of data error correction and further improving the data consistency of the distributed database.

Fig. 2 is a schematic diagram of the application scenario of the database processing method provided by the embodiment of the present application. As shown in Fig. 2, each data sub-server and backup sub-server in the distributed server can be used as physical sub-servers with different functions corresponding to the distributed database according to their respective functions. node. Wherein, the target data sub-server receiving the data processing request can be used as a computing node of the distributed database, the data sub-server storing the target data can be used as a storage node of the distributed database, and the backup sub-server can be used as a backup node. In addition, the coordination service component can be used as the coordination service node of the distributed database, and the coordination service node can be a virtual node and be set on the distributed server. The client and the distributed server can be connected through a proxy server. The proxy server can be a proxy node, which acts as an intermediate layer between the client and the distributed server, and is used to receive and forward the data processing sent by the client to the computing node of the distributed server. ask. A distributed database system is composed of clients, proxy nodes, computing nodes, storage nodes, backup nodes, and coordination service nodes. The nodes in the system are connected to each other in two-way communication, and can transmit query instructions and data, which is used to realize the embodiment of this application database processing method.

Fig. 3 is a flow chart of the steps of another database processing method provided by the embodiment of the present application. As shown in Fig. 3, the method includes: S1, performing face-to-face processing on the data processing code connected to the distributed database, and obtaining the lock with the target Resource-related lock resource parameters. S2. Obtain the target lock resource in the lock manager of the target data sub-server based on the target data sub-server. S3, obtain the target lock resource in the lock manager of other data sub-servers through the coordination service component. S4, according to whether the target lock resources in the lock managers of all data sub-servers are successfully obtained, execute the data processing code, or disconnect the client from the distributed database. S5. Acquiring the operation logs of each data sub-server based on the backup sub-server for backup. S6. When the backup sub-server finds the error log, it corrects the error data stored in the data sub-server according to the error log.

Fig. 4 is a structural diagram of a database processing device provided by an embodiment of the present application, the database processing device is applied to a distributed server, a distributed database is set on the distributed server, and the distributed server includes a plurality of data sub- server, the device 50 may include:

The determining module 501 is configured to receive a data processing request for the distributed database, and determine lock resource parameters according to lock resource information associated with target data in the data processing request; the target data is the data processing request request the data requested to be processed;

An acquisition module 502, configured to acquire a target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameter; the target lock resource is a lock resource corresponding to the target data;

The processing module 503 is configured to perform specified processing on the target data according to the operation indicated by the data processing request when the target lock resources in the lock managers of all the data sub-servers are successfully acquired.

Optionally, the data processing request includes a data processing code; the determining module 501 is specifically configured to:

receiving a data processing request for the distributed database through the target data sub-server in the distributed server;

performing aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code;

Determine lock resource parameters according to lock resource information associated with the target data in the lock resource subcode.

Optionally, the obtaining module 502 is specifically configured to:

Acquiring the target lock resource in the lock manager of the target data sub-server according to the lock resource parameter;

Synchronize the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server based on the preset registration nodes corresponding to the data sub-servers in the coordination service component;

For any of the other data sub-servers, the other data sub-server obtains the target lock resource in the lock manager of the other data sub-server according to the lock resource parameter.

Optionally, the acquiring module 502 is specifically further configured to:

Establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component;

sending the lock resource parameter to the coordination service component through the first connection based on the target data sub-server;

For any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, the lock resource parameter is sent to the other data sub-servers.

Optionally, the device 50 also includes:

The connection module is used for the acquisition module 502 to respond to the data processing request through the target data sub-server before acquiring the target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameters Establishing a second connection between the client and the distributed database; the client is a device that sends the data processing request to the target data sub-server;

The processing module 503 is specifically configured to: execute the data processing code based on the target data sub-server, so as to obtain data processing information from the client through the second connection, and process the data according to the data processing information. The target data in the distributed database is subjected to specified processing; the data processing code is used to implement the operation indicated by the data processing request.

Optionally, the device 50 also includes:

A disconnection module, configured to disconnect the second connection when the target lock resources in the lock managers of all the data sub-servers are not successfully obtained, so that other clients can establish with the distributed database Connect and process the data in the distributed database.

Optionally, the distributed server also includes a backup sub-server, and the device 50 also includes:

A storage module, configured to obtain the operation logs of each of the data sub-servers through the backup sub-server when the timing parameters in the backup sub-server meet the preset time requirements, and store the obtained operation logs in the in the backup subserver;

The error correction module is configured to correct the data in the data sub-server corresponding to the error log based on the backup sub-server when there is an error log in the operation log stored in the backup sub-server.

Optionally, the error correction module is specifically used for:

Based on the backup sub-server, determine error data according to the error log, and determine the data sub-server storing the error data as the first data sub-server;

Selecting a data sub-server storing correct data corresponding to the erroneous data as a second data sub-server according to the erroneous data;

Based on the backup sub-server, acquire the correct data in the second data sub-server, and replace the erroneous data in the first data sub-server with the correct data.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to part of the description of the method embodiment.

The database processing device has the same advantages as the above-mentioned database processing method over the prior art, and will not be repeated here.

The present application also provides an electronic device 60, referring to FIG. 5 , including: a processor 601, a memory 602, and a computer program 6021 stored in the memory 602 and operable on the processor 601, the processor 601 Implement the database processing method of the preceding embodiment when the program is executed.

The present application also provides a readable storage medium. When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device can execute the database processing method of the foregoing embodiments.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. The structure required to construct such a system is apparent from the above description. Furthermore, this application is not directed to any particular programming language. It should be understood that various programming languages can be used to implement the content of the application described here, and the description of specific languages above is to disclose the best implementation mode of the application.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be understood that in the above description of exemplary embodiments of the application, in order to streamline the application and to facilitate understanding of one or more of the various inventive aspects, various features of the application are sometimes grouped together in a single embodiment, figure, or in its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed application requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following this Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this application.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings), as well as any method or method so disclosed, may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

The various component embodiments of the present application may be realized in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the sorting device according to the present application. The present application can also be implemented as a device or an apparatus program for performing a part or all of the methods described herein. Such a program implementing the present application may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the application, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

The above is only a preferred embodiment of the application, and is not intended to limit the application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the application should be included in the scope of the application. within the scope of protection.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

It should be noted that the various data-related processes in this embodiment of the application are all carried out under the premise of complying with the corresponding data protection laws and policies of the country where the device is located, and with the authorization granted by the corresponding device owner.

Claims (13)

1. a database processing method, is characterized in that, is applied to distributed server, and described distributed server is provided with distributed database, and described distributed server comprises a plurality of data sub-servers, and described method comprises: Receive a data processing request for the distributed database, and determine lock resource parameters according to lock resource information associated with target data in the data processing request; the target data is the data requested to be processed by the data processing request ; According to the lock resource parameter, acquire the target lock resource in the lock manager of the target data sub-server in the distributed server; Synchronize the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server based on the preset registration nodes corresponding to the data sub-servers in the coordination service component; For any of the other data sub-servers, the other data sub-server obtains the target lock resource in the lock manager of the other data sub-server according to the lock resource parameter; the target lock resource is related to the target The lock resource corresponding to the data; In the case of successfully acquiring the target lock resources in the lock managers of all the data sub-servers, perform specified processing on the target data according to the operation indicated by the data processing request. 2. The method according to claim 1, wherein the data processing request includes a data processing code; the receiving the data processing request for the distributed database, and matching the target data according to the data processing request The associated lock resource information determines the lock resource parameters, including: receiving a data processing request for the distributed database through the target data sub-server; performing aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code; Determine lock resource parameters according to lock resource information associated with the target data in the lock resource subcode. 3. The method according to claim 1, wherein the registration node corresponding to each of the data sub-servers in the preset-based coordination service component synchronizes the lock resource parameters to all but all of the multiple data sub-servers Data subservers other than the above-mentioned target data subservers, including: Establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component; sending the lock resource parameter to the coordination service component through the first connection based on the target data sub-server; For any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, the lock resource parameter is sent to the other data sub-servers. 4. The method according to claim 2, wherein, before obtaining the target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameter, the method further comprises: In response to the data processing request, establishing a second connection between the client and the distributed database through the target data sub-server; the client is a device that sends the data processing request to the target data sub-server; The specified processing of the target data according to the operation indicated by the data processing request includes: Execute the data processing code based on the target data sub-server to obtain data processing information from the client through the second connection, and process the target data in the distributed database according to the data processing information Perform specified processing; the data processing code is used to implement the operation indicated by the data processing request. 5. method according to claim 4, is characterized in that, described method also comprises: If the target lock resources in the lock managers of all the data sub-servers are not successfully obtained, the second connection is disconnected, so that other clients can establish a connection with the distributed database and update the distributed database. Data in the database is processed. 6. The method according to claim 1, wherein the distributed server further comprises a backup sub-server, and the method further comprises: When the timing parameters in the backup sub-server meet the preset time requirements, obtain the operation logs of each of the data sub-servers through the backup sub-server, and store the obtained operation logs in the backup sub-server ; If there is an error log in the operation log stored by the backup sub-server, error correction is performed on the data in the data sub-server corresponding to the error log based on the backup sub-server. 7. The method according to claim 6, wherein the error correction of the data in the data sub-server corresponding to the error log based on the backup sub-server comprises: Based on the backup sub-server, determine error data according to the error log, and determine the data sub-server storing the error data as the first data sub-server; Selecting a data sub-server storing correct data corresponding to the erroneous data as a second data sub-server according to the erroneous data; Based on the backup sub-server, acquire the correct data in the second data sub-server, and replace the erroneous data in the first data sub-server with the correct data. 8. A database processing device, characterized in that it is applied to a distributed server, the distributed server is provided with a distributed database, the distributed server includes a plurality of data sub-servers, and the device includes: A determining module, configured to receive a data processing request for the distributed database, and determine lock resource parameters according to lock resource information associated with target data in the data processing request; the target data is the data processing request the data requested to be processed; An acquisition module, configured to acquire the target lock resource in the lock manager of the target data sub-server in the distributed server according to the lock resource parameter; Registering a node, synchronizing the lock resource parameters to other data sub-servers in the plurality of data sub-servers except the target data sub-server; for any of the other data sub-servers, through the other data sub-servers Obtaining the target lock resource in the lock manager of the other data sub-server according to the lock resource parameter; the target lock resource is a lock resource corresponding to the target data; The processing module is configured to perform specified processing on the target data according to the operation indicated by the data processing request when the target lock resources in the lock managers of all the data sub-servers are successfully acquired. 9. The device according to claim 8, wherein the data processing request includes a data processing code; the determining module is specifically used for: receiving a data processing request for the distributed database through the target data sub-server; performing aspect processing on the data processing code based on the target data sub-server, so as to separate the lock resource sub-code from the data processing code; Determine lock resource parameters according to lock resource information associated with the target data in the lock resource subcode. 10. The device according to claim 9, the acquiring module is further configured to: Establishing a first connection between the target data sub-server and the registration node corresponding to the target data sub-server in the preset coordination service component; sending the lock resource parameter to the coordination service component through the first connection based on the target data sub-server; For any of the other data sub-servers, based on the registration node corresponding to the other data sub-servers in the coordination service component, the lock resource parameter is sent to the other data sub-servers. 11. The device according to claim 8, further comprising: The connection module is used for the acquisition module to establish through the target data sub-server in response to the data processing request before acquiring the target lock resource in the lock manager of each of the data sub-servers according to the lock resource parameters. A second connection between the client and the distributed database; the client is a device that sends the data processing request to the target data sub-server; The processing module is specifically configured to: execute the data processing code based on the target data sub-server, so as to obtain data processing information from the client through the second connection, and process the distribution according to the data processing information. The specified processing is performed on the target data in the database; the data processing code is used to implement the operation indicated by the data processing request. 12. An electronic device, characterized in that it comprises: a processor, a memory, and a computer program stored on the memory and operable on the processor, when the processor executes the program, it realizes the The database processing method described in any one of 1-7. 13. A readable storage medium, wherein when the instructions in the storage medium are executed by the processor of the electronic device, the electronic device can execute the database processing method according to any one of claims 1-7.

Images