CN115470303B - Database access method, device, system, equipment and readable storage medium - Google Patents

Abstract

The application discloses a database access method, a device, a system, equipment and a readable storage medium in the technical field of computers. The method is applied to the virtual database, and the database access request can be routed to any target database node managed by the virtual database according to the load balancing strategy; the virtual database nano manages a plurality of MySQL database nodes, and all the MySQL database nodes share the same storage library; and enabling the target database node to complete the processing of the request by accessing the storage library. According to the method and the system, the master-slave concept of the database is abandoned, and all MySQL database nodes share the same repository instead, so that synchronous operation under a high concurrency scene can be avoided, data storage can be consistent, and stability, reliability and high availability of database access service can be guaranteed through load balancing. The database access device, the database access system, the database access equipment and the readable storage medium have the technical effects.

Description

A database access method, device, system, equipment and readable storage medium

technical field

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

Background technique

At present, in order to ensure the high availability and stable operation of the MySQL database service, a master node and a slave node are generally set up. Among them, the master node is used to handle write operations, and the slave node is used to handle query operations. Moreover, after the master node completes the write operation, it will synchronize the currently written data to the slave node. Therefore, if the amount of currently written data is large, the amount of synchronized data will be large. Therefore, in the case of a large number of write operations or low network bandwidth, there will be a delay in data synchronization, which will reduce the performance of database services.

Therefore, how to improve database service performance in a high-concurrency scenario is a problem to be solved by those skilled in the art.

Contents of the invention

In view of this, the purpose of the present application is to provide a database access method, device, system, equipment and readable storage medium, so as to improve the performance of database services in high concurrency scenarios. The specific plan is as follows:

In the first aspect, the present application provides a database access method applied to a virtual database, including:

Receive database access requests;

According to the load balancing strategy, the database access request is routed to any target database node managed by the virtual database; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same repository;

making the target database node complete the processing of the database access request by accessing the storage repository.

Optionally, the routing the database access request to any target database node managed by the virtual database according to the load balancing strategy includes:

Determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy;

Determining the MySQL database node with the least weight as the target database node, and routing the database access request to the target database node.

Optionally, the weight calculation process of any MySQL database node includes:

Calculate the routing frequency of the current MySQL database node;

Calculate the load score of the current MySQL database node at the current moment;

The sum of the route frequency and the load score is used as the weight of the current MySQL database node.

Optionally, the calculation of the routing frequency of the current MySQL database node includes:

Calculate the routing frequency of the current MySQL database node according to the first formula; the first formula is: W _u =C _i /C _S , W _u is the routing frequency of MySQL database node i, and C _i is the routing frequency of MySQL database node i The number of times to be routed, C _S is the preset maximum number of times to be routed.

Optionally, the calculation of the load score of the current MySQL database node at the current moment includes:

Calculate the load score of the current MySQL database node at the current moment according to the second formula; the second formula is: W _load = L _CPU × a + L _m × b + L _IO × c, W _load is the load of the current MySQL database node Scoring, L _CPU is the CPU load of the current MySQL database node, L _m is the memory load of the current MySQL database node, L _IO is the IO load of the current MySQL database node, and a, b, and c are preset coefficients.

Optionally, also include:

Regularly collect and record the operating status of all MySQL database nodes managed by the virtual database;

If any MySQL database node fails, add a failure identifier for the MySQL database node.

Optionally, also include:

During the operation of the virtual database, add, delete or modify the MySQL database nodes in the managed node sequence of the virtual database through a configuration update command to obtain an updated node sequence;

Manage and configure each MySQL database node in the updated node sequence one by one.

Optionally, the management and configuration of each MySQL database node in the updated node sequence one by one includes:

Determine the new MySQL database node in the updated node sequence;

After performing management and configuration on the newly added MySQL database nodes one by one, management and configuration are performed on the remaining MySQL database nodes in the updated node sequence.

Optionally, the management configuration of the newly added MySQL database node includes:

Configure the IP address, port, database account number and database login password of the newly added MySQL database node in the virtual database.

Optionally, also include:

Query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, access address, access port, virtual database account and virtual database login password.

Optionally, also include:

If the virtual database stops running, add, delete or modify the MySQL database nodes in the node sequence already managed by the virtual database, and restart the virtual database.

In a second aspect, the present application provides a database access device applied to a virtual database, including:

A receiving module, configured to receive a database access request;

A routing module, configured to route the database access request to any target database node managed by the virtual database according to a load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same repository;

A processing module, configured to enable the target database node to complete the processing of the database access request by accessing the storage repository.

Optionally, the routing module is specifically used for:

Determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy;

Determining the MySQL database node with the least weight as the target database node, and routing the database access request to the target database node.

Optionally, also include:

The health monitoring module is used to regularly collect and record the running status of all MySQL database nodes managed by the virtual database; if any MySQL database node fails, then add a failure identification for the MySQL database node.

Optionally, also include:

The node configuration online update module is used to add, delete or modify the MySQL database nodes in the node sequence managed by the virtual database through the configuration update command during the operation of the virtual database to obtain the updated node sequence ; Manage and configure each MySQL database node in the updated node sequence one by one.

Optionally, the node configuration online update module is specifically used to: determine the newly added MySQL database node in the updated node sequence; after managing and configuring the newly added MySQL database nodes one by one, the updated node sequence The rest of the MySQL database nodes in the management configuration.

Optionally, the node configuration online update module is specifically configured to: configure the IP address, port, database account number and database login password of the newly added MySQL database node in the virtual database.

Optionally, also include:

The service configuration operation module is used to query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, and the access address , access port, virtual database account and virtual database login password.

Optionally, also include:

The node configuration offline update module is used for adding, deleting or modifying the MySQL database nodes in the node sequence managed by the virtual database if the virtual database stops running, and restarting the virtual database.

In a third aspect, the present application provides a database access system, including: the virtual database disclosed above, multiple MySQL database nodes, and a storage library.

Optionally, the virtual database is used to: receive a database access request; route the database access request to any target database node managed by the virtual database according to a load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same storage repository; making the target database node complete the processing of the database access request by accessing the storage repository.

Optionally, the virtual database is used to: determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy; determine the MySQL database node with the smallest weight as the target database node , and route the database access request to the target database node.

Optionally, the virtual database is used to: calculate the routing frequency of the current MySQL database node; calculate the load score of the current MySQL database node at the current moment; use the sum of the routing frequency and the load rating as the current MySQL database node the weight of.

Optionally, the virtual database is used to: calculate the routing frequency of the current MySQL database node according to the first formula; the first formula is: W _u =C _i /C _S , and W _u is the routing frequency of the MySQL database node i , C _i is the routing times of MySQL database node i, and C _S is the preset maximum routing times.

Optionally, the virtual database is used to: calculate the load score of the current MySQL database node at the current moment according to the second formula; the second formula is: W _load =L _CPU ×a+L _m ×b+L _IO ×c, W _load is the load score of the current MySQL database node, L _CPU is the CPU load of the current MySQL database node, L _m is the memory load of the current MySQL database node, L _IO is the IO load of the current MySQL database node, and a, b, and c are all is the default coefficient.

Optionally, the virtual database is used to: regularly collect and record the running status of all the MySQL database nodes managed by the virtual database; if any MySQL database node fails, add a failure identifier for the MySQL database node.

Optionally, the virtual database is used for: during the operation of the virtual database, add, delete or modify the MySQL database nodes in the node sequence managed by the virtual database through a configuration update command to obtain updated nodes Sequence; manage and configure each MySQL database node in the updated node sequence one by one.

Optionally, the virtual database is used to: determine the newly added MySQL database nodes in the updated node sequence; after managing and configuring the newly added MySQL database nodes one by one, the remaining MySQL database nodes in the updated node sequence Make management configuration.

Optionally, the virtual database is used to: configure the IP address, port, database account and database login password of the newly added MySQL database node in the virtual database.

Optionally, the virtual database is used to: query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, Access address, access port, virtual database account and virtual database login password.

Optionally, the virtual database is used to: if the virtual database stops running, add, delete or modify MySQL database nodes in the node sequence already managed by the virtual database, and restart the virtual database.

In a fourth aspect, the present application provides an electronic device, including:

memory for storing computer programs;

A processor, configured to execute the computer program, so as to implement the database access method disclosed above.

In a fifth aspect, the present application provides a readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the aforementioned disclosed database access method is implemented.

It can be seen from the above solution that the present application provides a database access method applied to a virtual database, including: receiving a database access request; routing the database access request to any target database managed by the virtual database according to a load balancing strategy Node; Wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same storage; make the target database node complete the processing of the database access request by accessing the storage.

It can be seen that this application uses a virtual database to manage multiple MySQL database nodes sharing the same repository, and when receiving a database access request, the database access request can be routed to any target database node managed by the virtual database according to the load balancing strategy On, so that each MySQL database node can complete the processing of the database access request by accessing the repository. This solution abandons the concept of database master-slave and instead enables each MySQL database node to share the same repository, thereby not only avoiding synchronization operations in high-concurrency scenarios, thereby avoiding the impact of synchronization operations on database service performance, but also making the same database There is one copy of the data to ensure data consistency. Moreover, each database node managed by the virtual database can share access requests according to the load balancing strategy, so as to maximize the availability of each database node, thereby ensuring the stability, reliability and high availability of the entire database access service.

Correspondingly, the database access device, system, equipment and readable storage medium provided by the present application also have the above-mentioned technical effects.

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 are only It is an embodiment of the present application, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a flow chart of a database access method disclosed in the present application;

Fig. 2 is a schematic diagram of a database access system disclosed in the present application;

FIG. 3 is a schematic diagram of a database access device disclosed in the present application;

FIG. 4 is a schematic diagram of an electronic device disclosed in the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some of the embodiments of the 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 making creative efforts belong to the scope of protection of this application.

Currently, a MySQL database generally sets up a master node and a slave node. Among them, the master node is used to handle write operations, and the slave node is used to handle query operations. Moreover, after the master node completes the write operation, it will synchronize the currently written data to the slave node. Therefore, if the amount of currently written data is large, the amount of synchronized data will be large. Therefore, in the case of a large number of write operations or low network bandwidth, there will be a delay in data synchronization, which will reduce the performance of database services. For this reason, this application provides a database access scheme, which can enable each MySQL database node to share the same storage library, avoid the impact of synchronization operations on database service performance, and ensure the consistency of data storage and the stability of the entire database access service , reliability and high availability.

Referring to Fig. 1, the embodiment of the present application discloses a database access method applied to a virtual database, including:

S101. Receive a database access request.

In this embodiment, the database access request is: an SQL statement used to implement a query operation or an SQL statement used to implement a write operation. The virtual database in this embodiment can be understood as a software service, which can manage multiple MySQL database nodes at the same time. Library, thus realizing the shared storage service.

S102. Routing the database access request to any target database node managed by the virtual database according to the load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, and all the MySQL database nodes share the same storage library.

In one embodiment, routing the database access request to any target database node managed by the virtual database according to the load balancing strategy includes: determining the MySQL with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy Database node: determine the MySQL database node with the least weight as the target database node, and route the database access request to the target database node.

In one embodiment, the weight calculation process of any MySQL database node includes: calculating the routing frequency of the current MySQL database node; calculating the load score of the current MySQL database node at the current moment; the sum of the routing frequency and the load score, As the weight of the current MySQL database node. The current MySQL database node is: any node managed by the virtual database.

Wherein, calculating the routing frequency of the current MySQL database node includes: calculating the routing frequency of the current MySQL database node according to the first formula; the first formula is: W _u =C _i /C _S , W _u is the MySQL database node i Routing frequency, C _i is the routing times of MySQL database node i, and C _S is the preset maximum routing times.

Wherein, calculating the load score of the current MySQL database node at the current moment includes: calculating the load score of the current MySQL database node at the current moment according to the second formula; the second formula is: W _load =L _CPU ×a+L _m ×b+ L _IO × c, W _load is the load score of the current MySQL database node, L _CPU is the CPU load of the current MySQL database node, L _m is the memory load of the current MySQL database node, L _IO is the IO load of the current MySQL database node, a , b, c are preset coefficients. Generally, a+b+c=1.

S103. Make the target database node complete the processing of the database access request by accessing the storage repository.

Since the database access request is actually an SQL statement, the target database node can realize by executing the SQL statement: querying the corresponding information in the repository or writing some information into the repository.

It should be noted that the service configuration of the virtual database can be queried, added, deleted or modified according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, access address, access port, virtual Database account and virtual database login password.

It can be seen that in this embodiment, a virtual database is used to manage multiple MySQL database nodes that share the same repository, and when a database access request is received, the database access request can be routed to any target database managed by the virtual database according to the load balancing strategy Nodes, so that each MySQL database node can complete the processing of database access requests by accessing the repository. This solution abandons the concept of database master-slave and instead enables each MySQL database node to share the same repository, thereby not only avoiding synchronization operations in high-concurrency scenarios, thereby avoiding the impact of synchronization operations on database service performance, but also making the same database There is one copy of the data to ensure data consistency. Moreover, each database node managed by the virtual database can share access requests according to the load balancing strategy, so as to maximize the availability of each database node, thereby ensuring the stability, reliability and high availability of the entire database access service.

Based on the above embodiments, it should be noted that the virtual database can monitor the monitoring status of each MySQL database node managed by it. In one embodiment, the running status of all MySQL database nodes managed by the virtual database is regularly collected and recorded; if any MySQL database node fails, a failure identifier is added to the MySQL database node.

Of course, you can also flexibly adjust the MySQL database nodes managed by the virtual database, including online adjustment and offline adjustment. Online adjustment means: during the running process of the virtual database, add, delete or modify the MySQL database nodes in the node sequence managed by the virtual database through the configuration update command to obtain the updated node sequence; pair the updated node sequence one by one Each MySQL database node in the management configuration. Offline adjustment means: if the virtual database stops running, add, delete or modify the MySQL database nodes in the node sequence already managed by the virtual database, and restart the virtual database. Wherein, the managed node of the virtual database refers to a node that can be used to process requests. That is, a failed node or a node taken out of service is not in the node sequence.

Wherein, each MySQL database node in the updated node sequence is managed and configured one by one, including: determining a new MySQL database node in the updated node sequence; Manage and configure the remaining MySQL database nodes in the subsequent node sequence (for example, update the corresponding information when it is detected that the node IP, port and other information have been updated). Among them, the management configuration of the newly added MySQL database node includes: configuring the IP address, port, database account number and database login password of the newly added MySQL database node in the virtual database. For example: a MySQL database node is recorded as: IP:port:username:password in the node sequence.

It should be noted that prioritizing the configuration of new nodes can avoid service interruption. For example: the virtual database originally manages nodes A and B, and during an online adjustment, nodes A and B are changed to nodes C and D, then nodes C and D are configured first so that nodes C and D can accept access ask. If the nodes A and B are stopped from service first, the virtual database service will be interrupted.

Please refer to FIG. 2 , this embodiment provides a specific composition structure for the virtual database, including modules such as virtual service, configuration center, virtual service, load balancing, and health check. Among them, the relevant configuration information of the virtual database can be changed and read by means of the configuration center module, including: basic connection configuration and service configuration.

Among them, the basic connection configuration is used to set each node managed by the virtual database, and adopts the form of ip:port:username:password, which can record each node managed by the virtual database. For example: config.dbpool.serverList=10.0.0.1:3306:root:mysqladmin|10.0.0.2:3306:root:mysqladmin is the connection configuration corresponding to a certain node.

Among them, the service configuration includes: the maximum number of available connections, such as: config.dbpool.maxActive=100. The maximum number of idle connections, such as: config.dbpool.maxIdle=20. Initialize the number of connections, such as: config.dbpool.initSize=10. The maximum waiting time, in ms, such as: config.dbpool.maxWait=1000. Virtual database address and port, such as: config.server.url=10.1.1.1:3306. The virtual database access account and password can be multiple, such as: config.server.userInfo=root:mysqladmin|test1:test1. Of course, you can also set the user IP that can access the virtual database, such as: config.server.url:x=10.1.1.1:3306:root:mysqladmin, config.server.userInfo:x=root:mysqladmin|test1:test1, x For increasing Arabic numerals. It can be seen that multiple user IPs can be set to access the virtual database as required.

Both basic connection configuration and service configuration can be recorded in configuration files, and users can modify configuration files at any time. When the virtual database service starts, the configuration center will read the configuration file and assist other modules to complete the service initialization. After the service starts normally, the user can also query and modify related configurations through the following commands. For example: Use lssharedbconfig -i configName to query service configuration information, "-i" is an optional parameter, if not filled, all information will be returned, and if filled, specific configuration content will be returned. Use chgsharedbconfig -i configName configValue to modify service configuration information, "-i" is an optional parameter, this parameter has two parameter values, the first item is the configuration name, and the second item is the content of the configuration item. Use refreshsharedbconfig to read the configuration information and restart the virtual service.

It should be noted that the virtual database is an intermediate bridge between the underlying real database cluster and user service requests. The underlying database cluster is in a black-box state for users. Users will not directly access specific database nodes, but access virtual services provided by virtual databases, so that virtual services can route requests to specific database nodes. Therefore, the virtual service provides users with a unified access portal, which can shield the internal complex design and improve the simplicity of the system.

The load balancing module is a pre-function for virtual service routing. This module can select the most suitable node in the current database cluster for virtual service routing according to the set routing rules. This module can ensure that service requests can fall on each node as evenly as possible, providing the load capacity of the entire system. Among them, the load balancing routing rules include: (1) record the node routing times of the last 1000 requests, and calculate the usage weight score of each node (that is, the frequency of routing) for each routing. The calculation rule is: node routing times/total The number of routes is 1000. (2) Regularly scan the basic performance information of each node, including CPU usage, memory usage, and IO usage, and count the server load weight score (load score) of each node according to these three information. The calculation rules are: CPU usage*50+memory usage*30+IO usage*20. (3) Take the sum of the utilization weight score of each node and the server load weight score as the final load weight of the node, and the node with the lowest final load weight will be the target node of this routing.

The health check module regularly checks the health status of each database node and collects relevant data for use by the load balancing module. If a node fails, the load balancing module will recognize this event, and the node will no longer be included in the routing until the health check module reports that it is back to normal. This module is responsible for troubleshooting node failures in the system, and has the ability to automatically recover after the node is normal, ensuring the high availability of the entire system.

Among them, each database node in the database cluster (A, B, C, D as shown in Figure 2) uses shared storage as the data storage space, which can ensure the consistency of data storage. The instance information of each database node is registered in the virtual database through the configuration file. Start the virtual database service, and the configuration center will read the relevant configuration files. After reading, it will notify the health check module to perform operations such as connection and initialization of database nodes. The health check module checks the connectivity of each database node in turn, records the database nodes in a healthy state, and notifies the virtual service to route the request.

Among them, the capacity expansion or contraction of the database cluster can be expanded or contracted in the manner of expansion and contraction with shutdown and expansion and contraction with startup.

When expansion and contraction are stopped, the virtual service handles the shutdown state, and the user can directly modify the configuration file to change the database node list, restart the service after the change, and the expansion and contraction will take effect.

When starting to expand or shrink, the user can add or delete the database node list through the chgsharedbconfig command. The configuration center can detect the result of this command, and then notify the health check module to perform a new round of node health check and node connection initialization. At this time, each database node is initialized one by one to ensure that at least one node can process the access request during the whole process, so as to ensure the availability of the service, so as to avoid: when a new request comes in, no available database node can be found.

Please refer to Figure 2. The process of service request includes: After the request reaches the virtual service, the virtual service tries to obtain an available high-performance node through the load balancing module, that is, the load balancing module selects the health node with the lowest weight score from the current database cluster The node acts as a routing node and returns to the virtual service. At this time, the virtual service enables the routing node to execute an SQL statement to complete the service request to access the shared storage.

It can be seen that this embodiment provides a unified access portal for user requests, and establishes a multi-node database cluster based on shared storage, canceling the synchronization mechanism of the master and slave nodes. On the one hand, it can overcome the data synchronization delay when writing large amounts of data, and on the other hand, it can expand the number of nodes horizontally. Moreover, the unified access entrance shields the underlying cluster structure, and with the help of load balancing strategies, the database service can run normally under high concurrency and high pressure scenarios, ensuring the stability, reliability and high availability of the entire service.

A database access device provided in the embodiment of the present application is introduced below, and a database access device described below and a database access method described above may refer to each other.

Referring to Figure 3, the embodiment of the present application discloses a database access device, which is applied to a virtual database, including:

A receiving module 301, configured to receive a database access request;

The routing module 302 is used to route the database access request to any target database node managed by the virtual database according to the load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same repository;

The processing module 303 is configured to enable the target database node to complete the processing of the database access request by accessing the repository.

In one embodiment, the routing module is specifically used for:

Determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy;

The MySQL database node with the least weight is determined as the target database node, and the database access request is routed to the target database node.

In one embodiment, it also includes:

The health monitoring module is used to regularly collect and record the running status of all MySQL database nodes managed by the virtual database; if any MySQL database node fails, add a fault identification for the MySQL database node.

In one embodiment, it also includes:

The node configuration online update module is used to add, delete or modify the MySQL database nodes in the node sequence managed by the virtual database through the configuration update command during the operation of the virtual database to obtain the updated node sequence; update one by one Manage and configure each MySQL database node in the subsequent node sequence.

In one embodiment, the node configuration online update module is specifically used to: determine the newly added MySQL database node in the updated node sequence; Manage and configure the remaining MySQL database nodes.

In one embodiment, the node configuration online update module is specifically configured to: configure the IP address, port, database account number and database login password of the newly added MySQL database node in the virtual database.

In one embodiment, it also includes:

The service configuration operation module is used to query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, access address, access port, Virtual database account and virtual database login password.

In one embodiment, it also includes:

The node configuration offline update module is used to add, delete or modify the MySQL database nodes in the node sequence that the virtual database has managed if the virtual database stops running, and restart the virtual database.

For the more specific working process of each module and unit in this embodiment, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

It can be seen that this embodiment provides a database access device, which can enable each MySQL database node to share the same storage library, avoid the impact of synchronization operations on database service performance, and ensure the consistency of data storage and the stability of the entire database access service , reliability and high availability.

A database access device provided in the embodiment of the present application is introduced below, and a database access device described below and a database access method described above may be referred to each other.

The embodiment of the present application discloses a database access system, including: the virtual database disclosed in the foregoing embodiments, multiple MySQL database nodes, and a storage library. For details, refer to FIG. 2 , and the shared storage in FIG. 2 is the repository.

In one embodiment, the virtual database is used to: receive a database access request; route the database access request to any target database node managed by the virtual database according to the load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, And all the MySQL database nodes share the same repository; the target database node completes the processing of the database access request by accessing the repository.

In one embodiment, the virtual database is used to: determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy; determine the MySQL database node with the smallest weight as the target database node, and Database access requests are routed to target database nodes.

In one embodiment, the virtual database is used to: calculate the routing frequency of the current MySQL database node; calculate the load score of the current MySQL database node at the current moment; use the sum of the routing frequency and load scoring as the current MySQL database node Weights.

In one embodiment, the virtual database is used to: calculate the routing frequency of the current MySQL database node according to the first formula; the first formula is: W _u =C _i /C _S , where W _u is the routing frequency of the MySQL database node i degree, C _i is the routing times of MySQL database node i, and C _S is the preset maximum routing times.

In one embodiment, the virtual database is used to: calculate the load score of the current MySQL database node at the current moment according to the second formula; the second formula is: W _load =L _CPU ×a+L _m ×b+L _IO ×c , W _load is the load score of the current MySQL database node, L _CPU is the CPU load of the current MySQL database node, L _m is the memory load of the current MySQL database node, L _IO is the IO load of the current MySQL database node, a, b, c are preset coefficients.

In one embodiment, the virtual database is used to: regularly collect and record the running status of all MySQL database nodes managed by the virtual database; if any MySQL database node fails, add a failure identifier for the MySQL database node.

In one embodiment, the virtual database is used to: add, delete or modify the MySQL database nodes in the node sequence managed by the virtual database through configuration update commands during the running of the virtual database to obtain an updated node sequence ; Manage and configure each MySQL database node in the updated node sequence one by one.

In one embodiment, the virtual database is used to: determine the newly added MySQL database nodes in the updated node sequence; after managing and configuring the newly added MySQL database nodes one by one, the remaining MySQL databases in the updated node sequence Nodes are managed and configured.

In one embodiment, the virtual database is used to: configure the IP address, port, database account and database login password of the newly added MySQL database node in the virtual database.

In one embodiment, the virtual database is used to: query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, access Address, access port, virtual database account and virtual database login password.

In one embodiment, the virtual database is used to: if the virtual database stops running, add, delete or modify the MySQL database nodes in the node sequence already managed by the virtual database, and restart the virtual database.

An electronic device provided by an embodiment of the present application is introduced below, and the electronic device described below and the database access method and apparatus described above may refer to each other.

Referring to Figure 4, the embodiment of the present application discloses an electronic device, including:

Memory 401, used to store computer programs;

The processor 402 is configured to execute the computer program, so as to implement the method disclosed in any of the foregoing embodiments.

Further, the embodiment of the present application also provides a server as the above-mentioned electronic device. The server may specifically include: at least one processor, at least one memory, a power supply, a communication interface, an input and output interface, and a communication bus. Wherein, the memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement relevant steps in the database access method disclosed in any of the foregoing embodiments.

In this embodiment, the power supply is used to provide working voltage for each hardware device on the server; the communication interface can create a data transmission channel between the server and external devices, and the communication protocol it follows is applicable to the technical solution of this application Any communication protocol is not specifically limited here; the input/output interface is used to obtain external input data or output data to the external, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

In addition, memory, as a resource storage carrier, can be read-only memory, random access memory, magnetic disk or optical disk, etc. The resources stored on it include operating system, computer program and data, etc., and the storage method can be temporary storage or permanent storage.

Wherein, the operating system is used to manage and control various hardware devices and computer programs on the server, so as to realize the calculation and processing of the data in the memory by the processor, which may be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the database access method disclosed in any of the foregoing embodiments, the computer program can further include a computer program that can be used to complete other specific tasks. In addition to data such as the virtual machine, the data may also include data such as developer information of the virtual machine.

Further, the embodiment of the present application also provides a terminal as the above-mentioned electronic device. The terminal specifically may include, but is not limited to, a smart phone, a tablet computer, a notebook computer or a desktop computer, and the like.

Generally, the terminal in this embodiment includes: a processor and a memory.

Wherein, the processor may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor can be realized by at least one hardware form of DSP (Digital Signal Processing, digital signal processing), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array, programmable logic array) . The processor can also include a main processor and a coprocessor, the main processor is a processor for processing data in the wake-up state, also called a CPU (Central Processing Unit, central processing unit); Low-power processor for processing data in standby state. In some embodiments, the processor may be integrated with a GPU (Graphics Processing Unit, image processor), and the GPU is used for rendering and drawing content that needs to be displayed on the display screen. In some embodiments, the processor may further include an AI (Artificial Intelligence, artificial intelligence) processor, where the AI processor is configured to process computing operations related to machine learning.

The memory may include one or more computer-readable storage media, which may be non-transitory. Memory may also include high-speed random access memory, and non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory is at least used to store the following computer program, wherein, after the computer program is loaded and executed by the processor, it can implement the relevant steps in the database access method performed by the terminal side disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory may also include an operating system and data, etc., and the storage method may be temporary storage or permanent storage. Wherein, the operating system may include Windows, Unix, Linux and so on. Data may include, but is not limited to, application update information.

In some embodiments, the terminal may further include a display screen, an input/output interface, a communication interface, a sensor, a power supply, and a communication bus.

A readable storage medium provided by an embodiment of the present application is introduced below. The readable storage medium described below and the database access method, device, and device described above may refer to each other.

A readable storage medium is used to store a computer program, wherein when the computer program is executed by a processor, the database access method disclosed in the foregoing embodiments is implemented.

"First", "second", "third", "fourth" and the like referred to in the present application, if any, are used to distinguish similar objects and not necessarily to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, e.g. a process, method or apparatus comprising a series of steps or elements is not necessarily limited to those steps or elements explicitly listed , but may include other steps or elements not explicitly listed or inherent to the process, method or apparatus.

It should be noted that the descriptions in this application involving "first", "second" and so on are for descriptive purposes only, and should not be understood as indicating or implying their relative importance or implicitly indicating the number of indicated technical features . Thus, the features defined as "first" and "second" may explicitly or implicitly include at least one of these features. In addition, the technical solutions of the various embodiments can be combined with each other, but it must be based on the realization of those skilled in the art. When the combination of technical solutions is contradictory or cannot be realized, it should be considered that the combination of technical solutions does not exist , nor within the scope of protection required by the present application.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known readable storage medium.

In this paper, specific examples are used to illustrate the principles and implementation methods of the application. The descriptions of the above embodiments are only used to help understand the method and core idea of the application; meanwhile, for those of ordinary skill in the art, according to the application There will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be construed as limiting the application.

Claims (13)

1. A database access method, characterized in that being applied to a virtual database, comprising: Receive database access requests; According to the load balancing strategy, the database access request is routed to any target database node managed by the virtual database; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share the same repository; The virtual database described above makes all MySQL database nodes in a black box state for users; enabling the target database node to complete the processing of the database access request by accessing the repository; Among them, also include: During the operation of the virtual database, add, delete or modify the MySQL database nodes that have been managed by the virtual database by configuring an update command to obtain an updated node sequence; Manage and configure each MySQL database node in the updated node sequence one by one; Wherein, each MySQL database node in the updated node sequence is managed and configured one by one, including: Determine the new MySQL database node in the updated node sequence; After performing management and configuration on the newly added MySQL database nodes one by one, management and configuration are performed on the remaining MySQL database nodes in the updated node sequence. 2. The method according to claim 1, wherein the routing the database access request to any target database node managed by the virtual database according to the load balancing strategy comprises: Determine the MySQL database node with the smallest weight among all the MySQL database nodes managed by the virtual database according to the load balancing strategy; Determining the MySQL database node with the least weight as the target database node, and routing the database access request to the target database node. 3. method according to claim 2, is characterized in that, the weight calculation process of any MySQL database node comprises: Calculate the routing frequency of the current MySQL database node; Calculate the load score of the current MySQL database node at the current moment; The sum of the route frequency and the load score is used as the weight of the current MySQL database node. 4. method according to claim 3, is characterized in that, the route frequency degree of described computing current MySQL database node, comprises: Calculate the routing frequency of the current MySQL database node according to the first formula; the first formula is: W _u =C _i /C _S , W _u is the routing frequency of MySQL database node i, and C _i is the routing frequency of MySQL database node i The number of times to be routed, C _S is the preset maximum number of times to be routed. 5. The method according to claim 3, wherein the calculation of the load rating of the current MySQL database node at the current moment comprises: Calculate the load score of the current MySQL database node at the current moment according to the second formula; the second formula is: W _load = L _CPU × a + L _m × b + L _IO × c, W _load is the load of the current MySQL database node Scoring, L _CPU is the CPU load of the current MySQL database node, L _m is the memory load of the current MySQL database node, L _IO is the IO load of the current MySQL database node, and a, b, and c are preset coefficients. 6. The method according to any one of claims 1 to 5, further comprising: Regularly collect and record the operating status of all MySQL database nodes managed by the virtual database; If any MySQL database node fails, add a failure identifier for the MySQL database node. 7. The method according to any one of claims 1 to 5, wherein the management and configuration of the newly added MySQL database node includes: Configure the IP address, port, database account number and database login password of the newly added MySQL database node in the virtual database. 8. The method according to any one of claims 1 to 5, further comprising: Query, add, delete or modify the service configuration of the virtual database according to user operations; the service configuration includes: the maximum number of available connections, the maximum number of idle connections, the longest waiting time, access address, access port, virtual database account and the virtual database login password. 9. The method according to any one of claims 1 to 5, further comprising: If the virtual database stops running, add, delete or modify the MySQL database nodes managed by the virtual database, and restart the virtual database. 10. A database access device, characterized in that it is applied to a virtual database, comprising: A receiving module, configured to receive a database access request; A routing module, configured to route the database access request to any target database node managed by the virtual database according to a load balancing strategy; wherein, the virtual database manages multiple MySQL database nodes, and all MySQL database nodes share The same repository; said virtual database makes all MySQL database nodes in a black-box state to the user; a processing module, configured to enable the target database node to complete the processing of the database access request by accessing the storage; Among them, also include: The node configuration online update module is used to add, delete or modify the MySQL database nodes that have been managed by the virtual database through configuration update commands during the running process of the virtual database, so as to obtain an updated node sequence; update one by one Manage and configure each MySQL database node in the following node sequence; Wherein, the node configuration online update module is specifically used for: Determine the new MySQL database node in the updated node sequence; After performing management and configuration on the newly added MySQL database nodes one by one, management and configuration are performed on the remaining MySQL database nodes in the updated node sequence. 11. A database access system, comprising: a virtual database according to any one of claims 1 to 10, a plurality of MySQL database nodes and a storage repository. 12. An electronic device, characterized in that it comprises: memory for storing computer programs; A processor, configured to execute the computer program to implement the method according to any one of claims 1-9. 13. A readable storage medium, characterized by being used to store a computer program, wherein the computer program implements the method according to any one of claims 1 to 9 when executed by a processor.

Images