CN114925052A - Method, device, equipment and computer readable medium for restarting database - Google Patents

Abstract

The invention discloses a method, a device, equipment and a computer readable medium for restarting a database, and relates to the technical field of computers. One embodiment of the method comprises: stopping and restarting the database backup in response to the remote procedure call request; under the condition that the data in the database main library and the data in the database standby library are consistent, transferring a data request from the database main library to the database standby library; switching the database main library into a new database standby library and switching the database standby library into a new database main library; and restarting the database to prepare the database newly. This embodiment enables the database to shorten the unavailability time period.

Description

Method, apparatus, device and computer readable medium for restarting a database

technical field

The present invention relates to the field of computer technologies, and in particular, to a method, apparatus, device and computer-readable medium for restarting a database.

Background technique

MySQL is a relational database management system, relational databases keep data in different tables instead of keeping all the data in one big warehouse, which increases speed and improves flexibility. The SQL language used by MySQL is the most commonly used standardized language for accessing databases.

At present, the restart plan of ApsaraDB for MySQL usually deploys the agent service and the MySQL service in a container. Then the management and control system calls the Remote Procedure Call (RPC) interface exposed by the Agent service to restart the main database and the standby database respectively.

In the process of implementing the present invention, the inventor finds that there are at least the following problems in the prior art: the MySQL database restart solution often causes the database to be unavailable for a long time.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide a method, apparatus, device, and computer-readable medium for restarting a database, which can shorten the unavailable time of the database.

To achieve the above object, according to an aspect of the embodiments of the present invention, a method for restarting a database is provided, including:

In response to a remote procedure call request, stop and restart the database standby database;

When the data in the main database and the standby database are consistent, transfer the data request from the main database to the standby database;

Switching the database main database to a new database standby database, and switching the database standby database to a new database main database;

Restart the new standby database of the database.

The data in the main database database and the database backup database are consistent, including:

Speed up the writing speed of the database standby database;

When the delay time between the main database and the standby database is less than or equal to a preset delay threshold, the main database is set to read-only;

Based on the location information of the main database database and the location information of the standby database database, it is determined that the data in the main database database and the standby database database are consistent.

The transferring the data request from the main database to the standby database includes:

In load balancing, the IP of the main database database is deleted, and the IP of the standby database database is configured in the load balancing, so as to transfer data requests from the main database database to the standby database database.

The switching of the main database database to the new standby database database includes:

cleaning up the synchronization information in the database standby database;

Connect the main database database, and add replication information for the main database database, so as to switch the main database database to a new database backup database;

The switching of the database standby database to the new main database database includes:

The read-only of the database standby database is turned on, and the disk write policy is reset, and the database standby database is switched to the new main database of the database.

Before stopping and restarting the database standby database in response to the remote procedure call request, the method further includes:

The master-slave delay between the database master database and the database slave database is less than a preset restart threshold.

The method also includes:

If the master-slave delay between the master database and the slave database is greater than or equal to a preset restart threshold, the master database and the slave database are forcibly restarted.

Before switching the main database database to the new standby database, and switching the standby database to the new main database, the method further includes:

Supports delayed switching, and detects that the current time is consistent with the specified switching time.

According to a second aspect of the embodiments of the present invention, an apparatus for restarting a database is provided, including:

The response module is used to stop and restart the database standby database in response to the remote procedure call request;

a transfer module, configured to transfer a data request from the main database database to the standby database database under the condition that the data in the main database database and the standby database database are consistent;

A switching module, used for switching the main database database to a new standby database, and switching the standby database to a new main database;

The restart module is used for restarting the new standby database of the database.

According to a third aspect of the embodiments of the present invention, an electronic device for restarting a database is provided, including:

one or more processors;

storage means for storing one or more programs,

The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

According to a fourth aspect of the embodiments of the present invention, there is provided a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned method is implemented.

An embodiment of the above invention has the following advantages or beneficial effects: in response to a remote procedure call request, stop and restart the database standby database; when the data in the main database database and the database standby database are consistent, the data request is sent from all The main database is transferred to the standby database; the main database is switched to the new standby database, and the standby database is switched to the new main database; the new standby database is restarted. Under the condition that the data of the main database database and the database standby database are consistent, the main database database and the database standby database are exchanged, thereby reducing the occupied time of restarting the database, and then shortening the unavailable time of the database.

Further effects of the above non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present invention and do not constitute an improper limitation of the present invention. in:

1 is a schematic flowchart of a main flow of a method for restarting a database according to an embodiment of the present invention;

2 is a schematic diagram of a forced restart of a database according to an embodiment of the present invention;

3 is a schematic flowchart of determining the consistency of data in the main database database and the database standby database according to an embodiment of the present invention;

4 is a schematic diagram of a transfer data request according to an embodiment of the present invention;

5 is a schematic flowchart of switching the main database database to the new standby database database according to an embodiment of the present invention;

6 is a schematic diagram of a handover database according to an embodiment of the present invention;

7 is a schematic flowchart of restarting a database according to an embodiment of the present invention;

8 is a schematic diagram of the main structure of an apparatus for restarting a database according to an embodiment of the present invention;

FIG. 9 is an exemplary system architecture diagram to which an embodiment of the present invention may be applied;

FIG. 10 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

At present, the MySQL database restart scheme often causes the database to be unavailable for a long time. For example, if you restart directly, each restart will cause the service to be unavailable for a long time. The average impact time is more than 2 minutes, resulting in poor user experience.

In order to solve the technical problem that the MySQL database is unavailable for a long time, the following technical solutions in the embodiments of the present invention may be adopted.

Referring to FIG. 1 , FIG. 1 is a schematic diagram of the main flow of a method for restarting a database according to an embodiment of the present invention. When the data in the main database database and the database standby database are consistent, the main database database and the database standby database are switched. As shown in Figure 1, it specifically includes the following steps:

S101, in response to the remote procedure call request, stop and restart the database standby database.

In this embodiment of the present invention, the Agent service and the MySQL service are deployed in a container. That is to say, the main library container includes the agent service and the database main library; the standby library container includes the agent service and the database standby library. The database master database and the database standby database are both relative and belong to the database. The database standby database serves as the data backup of the database main database. The user is responsible for manipulating the database through the management and control system.

In order to restart the database, the management and control system sends an RPC request, calls the proxy service of the database standby database, stops using the database standby database, and restarts the database standby database. As an example, the method of restarting the database standby database includes forcibly restarting the database standby database through an RPC request. As another example, if the forced restart of the database standby database fails through an RPC request, the Secure Shell Protocol (SSH) is used to connect to the standby database container, and remote commands are executed instead of RPC operations.

Referring to FIG. 2, FIG. 2 is a schematic diagram of forcibly restarting a database according to an embodiment of the present invention. In Figure 2, the management and control system controls the database standby database through RPC requests or SHH.

In order to restart the database standby database, the management and control system sends an RPC request, and through the proxy service, first stop the database standby database (systemctl stop mysqld), and then start the database standby database (systemctl start mysqld).

If the invocation of the RPC request fails or the invocation of the RPC request times out, you can use the SHH method to connect to the standby container and execute remote commands instead of RPC operations. When using SSH, you can directly forcibly kill the database (pkill-9mysqld).

Understandably, SSH is used only if the call to RPC fails. Invoking RPC requests depends on the proxy service deployed in the container. Once the proxy service is abnormal, the proxy service cannot be called, that is, the database standby database cannot be restarted. Therefore, an alternate solution is adopted, using SSH to directly connect to the container, and execute the SHELL command to operate the database.

S102: In the case that the data in the main database and the standby database are consistent, transfer the data request from the main database to the standby database.

In the embodiment of the present invention, restarting the database includes restarting the database standby database and the database main database. In order to restart the database master database, the premise is to ensure that the data in the database master database and the database standby database are consistent. When the data in the main database database and the database standby database are consistent, the data request is transferred from the database main database to the database standby database.

Referring to FIG. 3, FIG. 3 is a schematic flowchart of determining the consistency of data in the main database database and the database standby database according to an embodiment of the present invention. Specifically include the following steps:

S301. Speed up the writing speed of the database standby database.

In order to shorten the time-consuming of restarting the database, the proxy service of the database standby database is requested through RPC. The proxy service connects to the database standby database and sets the disk write policy to speed up the writing speed of the database standby database. For example: set globalinnodb_flush_log_at_trx_commit=2; set global sync_binlog=0.

S302. The delay time between the main database database and the database standby database is less than or equal to a preset delay threshold, and the database main database is set to read-only.

Usually the storage delay time between the database master database and the database standby database. If the delay time between the database master database and the database standby database is less than or equal to the preset delay threshold, it means that the database master database and the database standby database can be synchronized, and the database master database is set to read-only. That is, set global read_only='on'. The purpose of setting read-only is to stop writing to the main database database to ensure that the database standby database quickly catches up with the main database.

As an example, the preset delay threshold is 10 seconds. By sending an RPC request to the proxy service of the database standby database, the proxy service connects to the database and executes: show slave status to obtain the delay time.

S303. Based on the location information of the main database database and the location information of the standby database database, it is determined that the data in the main database database and the standby database database are consistent.

After setting the database master database to be read-only, you need to make sure that the data in the database master database and the database standby database are consistent based on the location information of the database master database and the database standby database.

As an example, the RPC request is sent to the proxy service in the main database container and the proxy service in the standby database container respectively. To connect to the database through the proxy service, obtain the location information of the main database database and the location information of the database standby database respectively. For example: use select@@global.gtid_executed to obtain site information. Site information is used to record the identification of database synchronization data.

In the specific implementation, if the difference between the location information of the main database database and the location information of the database standby database, that is, the location difference is 0, it is determined that the data in the main database database and the database standby database are consistent.

In the embodiment of FIG. 3 , on the one hand, the writing speed of the database backup database is accelerated;

When the data in the main database database and the database standby database are consistent, the data request is transferred from the database main database to the database standby database. That is, the main database database no longer processes data requests, and the database standby database is responsible for processing data requests.

In an embodiment of the present invention, when the data in the main database and the standby database are consistent, the data request can be transferred from the main database to the standby database. Specifically, in the load balancing, delete the IP of the database master database, and configure the IP of the database backup database into the load balancing, so as to transfer data requests from the database master database to the database backup database. In this way, the main database library no longer directly provides read and write services.

Load Balance (LB) refers to balancing and apportioning loads (work tasks) to multiple operation units for operation. So as to complete the work tasks together. Load balancing is built on the original network structure. It provides a transparent and cheap and effective method to expand the bandwidth of servers and network equipment, strengthen the network data processing capacity, increase the throughput, and improve the availability and flexibility of the network.

Referring to FIG. 4, FIG. 4 is a schematic diagram of a transfer data request according to an embodiment of the present invention. In Figure 4, in the main database of the database, data is exchanged with MySQL through the agent service (Agent); in the standby database of the database, data is exchanged with MySQL through the Agent. During the load balancing process, users transfer data requests from the main database to the standby database. The main database database does not need to participate in load balancing, and the database standby database participates in load balancing. The master-slave synchronization is implemented between the database master database and the database standby database, that is, the data in the database master database is synchronized to the database standby database.

S103, switch the main database database to the new standby database, and switch the standby database to the new main database of the database.

The data request has been transferred from the database main database to the database standby database, which means that the role of the database standby database at this time is the main database, and the role of the database main database at this time is the standby database. Further, it is necessary to switch the main database database to the new database standby database, and to switch the database standby database to the new database main database.

Referring to FIG. 5 , FIG. 5 is a schematic flowchart of switching the main database database to the new standby database database according to an embodiment of the present invention. Specifically include the following steps:

S501. Clean up the synchronization information in the database standby database.

Through the RPC request, through the proxy service of the database standby database, the synchronization information in the standby database is cleaned up. As an example, the synchronization information includes slave information, and the following commands are used to implement cleanup: stop slave; reset slave all.

S502: Connect to the main database database, and add replication information to the main database database, so as to switch the main database database to the new standby database database.

Through the RPC request, the proxy service of the database master database and the replication information are added to the database master database to switch the database master database to the new database standby database. As an example, add replication information for the database master database in the following manner: change master to master_host='master_host', master_port='master_port', master_auto_position=1; start slaveuser='replicater' password='replicater'.

In the embodiment of FIG. 5 , the main database database is switched to the new standby database database.

Similarly, switch the database standby database to the new primary database: turn on the read-only of the database standby database, and reset the disk write policy to switch the database standby database to the new primary database of the database. Specifically, the following command is used to open the new main database of the database: set global read_only='off'. Reset the disk write policy: set global innodb_flush_log_at_trx_commit=1; set globalsync_binlog=1.

At this point, switch the database main database to the new database standby database, and switch the database standby database to the new database main database;

Referring to FIG. 6, FIG. 6 is a schematic diagram of a handover database according to an embodiment of the present invention. In FIG. 6, the following master-slave synchronization is deleted, that is, the master-slave synchronization from the database master database to the database backup database is deleted. Establish the following master-slave synchronization, namely: establish the master-slave synchronization from the database standby database to the database master database.

S104. Restart the database to a new standby database.

Since the new standby database of the database has not been restarted, it is necessary to restart the new standby database of the database. Specifically, an RPC request is used to stop and start the new database standby database through the proxy server of the new database standby database. Make sure that the new standby database of the database has been restarted. Among them, if the RPC request fails to restart or times out, the forced restart in FIG. 2 may also be used.

In one embodiment of the present invention, the handover time may also be supported for the handover database. That is, it supports delayed switching and detects whether the current time is consistent with the specified switching time. If the current time is consistent with the specified switching time, the main database will be switched to the new standby database, and the standby database will be switched to the new primary database; if the current time is inconsistent with the specified switching time, There is no need to switch databases.

The database is switched based on the specified switching time, mainly considering that the restart impact time is short enough, and there is only a few seconds of read-only time. But I also don't want the above read-only time to appear during peak business hours. Therefore, you can designate a low business peak period to complete the database switch. As an example, the specified switching time is set according to the low traffic peak period.

In the specific implementation process, after restarting the database standby database, it is determined that the current time is inconsistent with the specified switching time, the current task is suspended, and the task to be dispatched is added. Regularly check tasks to be dispatched, support delayed switching, and execute tasks to be dispatched when the current time is consistent with the specified switching time.

In an embodiment of the present invention, there are many ways to restart the database. In addition to the technical solutions of S101 to S104, forced restart may also be directly adopted.

The way to restart the database can be determined based on the master-slave delay between the database master database and the database slave database. Specifically, if the master-slave delay between the database master database and the database slave database is less than the preset restart threshold, the technical solutions from S101 to S104 are adopted, which is convenient to speed up the data synchronization between the database master database and the database slave database; the database master database and the database slave database The master-slave delay of the library is greater than or equal to the preset restart threshold, and the forced restart is as described above.

That is to say, when restarting the database, the restart method may not be specified. Use RPC request to pass through the proxy service of the database slave library, the proxy service connects to the database slave library, and obtains the delay time. For example, execute show slave status to get the delay time to determine how to restart the database.

In the above embodiment, in response to a remote procedure call request, stop and restart the database standby database; if the data in the database main database and the database standby database are consistent, transfer the data request from the database main database to the database standby database. database backup database; switching the main database database to a new database backup database, and switching the database backup database to a new database primary database; restarting the new database backup database. Under the condition that the data of the main database database and the database standby database are consistent, the main database database and the database standby database are exchanged, thereby reducing the occupied time of restarting the database, and then shortening the unavailable time of the database.

Referring to FIG. 7, FIG. 7 is a schematic flowchart of restarting a database according to an embodiment of the present invention. Specifically include the following steps:

S701. Restart the database.

After receiving the restart instruction, restart the database. Determines the way to restart the database based on the master-slave latency. If the master-slave delay is greater than or equal to 10 seconds, execute S702; if the master-slave delay is less than 10 seconds, execute S704.

S702. Restart the main database of the database.

Force restart of the main database database.

S703. Restart the database standby database.

Force restart the database standby database.

S704, restart the database standby database.

Use RPC request to restart the database standby database through the proxy service.

S705. Determine whether the current time is consistent with the switching time.

Determine whether the current time is consistent with the specified switching time. If the current time is inconsistent with the designated switching time, S706 is executed; if the current time is consistent with the designated switching time, S707 is executed.

S706, suspend the current task.

In order to avoid the impact of switching databases on the business, the current task needs to be suspended. Then, it is judged again whether the current time is consistent with the designated switching time.

S707. Switch the database.

Switch the database primary database to the new database standby database, and switch the database standby database to the new database primary database.

S708. Restart the database and the new standby database.

After restarting the database and the new standby database, restart the database.

In the embodiment of FIG. 7 , S702 to S703 are steps of forced restart; S704 to S708 are steps of smooth restart. Through S701, it can be judged which way to restart the database. Of course, forced restart or graceful restart can also be used directly.

Referring to FIG. 8, FIG. 8 is a schematic diagram of the main structure of an apparatus for restarting a database according to an embodiment of the present invention. The apparatus for restarting a database can implement a method for restarting a database. As shown in FIG. 8, the apparatus for restarting the database specifically includes:

The response module 801 is used to stop and restart the database standby database in response to the remote procedure call request;

A transfer module 802, configured to transfer a data request from the main database database to the standby database database when the data in the main database database and the standby database database are consistent;

A switching module 803, configured to switch the main database database to a new standby database, and to switch the standby database to a new main database;

The restarting module 804 is used for restarting the new standby database of the database.

In an embodiment of the present invention, the transfer module 802 is specifically configured to speed up the writing speed of the database standby database;

When the delay time between the main database and the standby database is less than or equal to a preset delay threshold, the main database is set to read-only;

Based on the location information of the main database database and the location information of the standby database database, it is determined that the data in the main database database and the standby database database are consistent.

In an embodiment of the present invention, the transfer module 802 is specifically configured to delete the IP of the main database database in load balancing, and configure the IP of the database backup database into the load balancing, so as to transfer the data The request is transferred from the database master database to the database backup database.

In an embodiment of the present invention, the switching module 803 is specifically configured to clear the synchronization information in the database standby database;

Connect the main database database, and add replication information for the main database database, so as to switch the main database database to a new database backup database;

as well as,

The read-only of the database standby database is turned on, and the disk write policy is reset, and the database standby database is switched to the new main database of the database.

In an embodiment of the present invention, the response module 801 is further configured for the master-slave delay between the database master database and the database slave database, which is less than a preset restart threshold.

In an embodiment of the present invention, the response module 801 is further configured to forcibly restart the master database and all the master-slave delays between the master database and the slave database if the delay is greater than or equal to a preset restart threshold. Describe the database standby database.

In an embodiment of the present invention, the switching module 803 is further configured to support delayed switching, and detect that the current time is consistent with the specified switching time.

FIG. 9 shows an exemplary system architecture 900 of a method for restarting a database or an apparatus for restarting a database to which embodiments of the present invention can be applied.

As shown in FIG. 9 , the system architecture 900 may include terminal devices 901 , 902 , and 903 , a network 904 and a server 905 . The network 904 is a medium used to provide a communication link between the terminal devices 901 , 902 , 903 and the server 905 . Network 904 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 901, 902, 903 to interact with the server 905 through the network 904 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 901 , 902 and 903 , such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

The terminal devices 901, 902, 903 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 905 may be a server that provides various services, such as a background management server that supports shopping websites browsed by the terminal devices 901 , 902 , and 903 (just an example). The background management server can analyze and process the received product information query request and other data, and feed back the processing results (such as target push information, product information—just an example) to the terminal device.

It should be noted that the method for restarting the database provided by the embodiment of the present invention is generally executed by the server 905 , and accordingly, the apparatus for restarting the database is generally set in the server 905 .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 9 are only illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Referring to FIG. 10 below, it shows a schematic structural diagram of a computer system 1000 suitable for implementing a terminal device according to an embodiment of the present invention. The terminal device shown in FIG. 10 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present invention.

As shown in FIG. 10, a computer system 1000 includes a central processing unit (CPU) 1001, which can be loaded into a random access memory (RAM) 1003 according to a program stored in a read only memory (ROM) 1002 or a program from a storage section 1008 Instead, various appropriate actions and processes are performed. In the RAM 1003, various programs and data necessary for the operation of the system 1000 are also stored. The CPU 1001 , the ROM 1002 , and the RAM 1003 are connected to each other through a bus 1004 . An input/output (I/O) interface 1005 is also connected to the bus 1004 .

The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc. ; and a communication section 1009 including a network interface card such as a LAN card, a modem, and the like. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 1010 as needed so that a computer program read therefrom is installed into the storage section 1008 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as computer software programs in accordance with the disclosed embodiments of the present invention. For example, embodiments disclosed herein include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 1009, and/or installed from the removable medium 1011. When the computer program is executed by the central processing unit (CPU) 1001, the above-described functions defined in the system of the present invention are executed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The modules involved in the embodiments of the present invention may be implemented in a software manner, and may also be implemented in a hardware manner. The described modules can also be provided in the processor, for example, it can be described as: a processor includes a response module, a transfer module, a switch module and a restart module. Among them, the names of these modules do not constitute a limitation of the module itself under certain circumstances. For example, the response module can also be described as "used to stop and restart the database standby database in response to a remote procedure call request".

As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device includes:

In response to a remote procedure call request, stop and restart the database standby database;

When the data in the main database and the standby database are consistent, transfer the data request from the main database to the standby database;

Switching the database main database to a new database standby database, and switching the database standby database to a new database main database;

Restart the new standby database of the database.

According to the technical solution of the embodiment of the present invention, in response to a remote procedure call request, stop and restart the database standby database; when the data in the database main database and the database standby database are consistent, transfer the data request from the database main database to the database standby database; switching the database main database to a new database standby database, and switching the database standby database to a new database main database; restarting the new database standby database. Under the condition that the data of the main database database and the database standby database are consistent, the main database database and the database standby database are exchanged, thereby reducing the occupied time of restarting the database, and then shortening the unavailable time of the database.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method of restarting a database, comprising:

stopping and restarting the database backup in response to the remote procedure call request;

under the condition that the data in the database main library and the data in the database standby library are consistent, transferring the data request from the database main library to the database standby library;

switching the database main library into a new database standby library and switching the database standby library into a new database main library;

and restarting the new database.

2. The method for restarting the database according to claim 1, wherein the data in the database master library and the database backup library are consistent, comprising:

accelerating the writing speed of the database standby library;

setting the database master library as read-only when the delay time of the database master library and the database standby library is less than or equal to a preset delay threshold;

and determining that the data in the database main library and the data in the database standby library are consistent based on the site information of the database main library and the site information of the database standby library.

3. The method of restarting a database according to claim 1 wherein said transferring a data request from said database master library to said database backup library comprises:

and in the load balancing, deleting the IP of the database main library, and configuring the IP of the database standby library into the load balancing so as to transfer the data request from the database main library to the database standby library.

4. The method for restarting the database according to claim 1, wherein said switching the database master library to the database backup library comprises:

cleaning the synchronous information in the database standby database;

connecting the database master library, and adding replication information for the database master library to switch the database master library into a new database standby library;

the switching the database standby database into a new database main database comprises the following steps:

and opening the read-only of the database standby library, resetting a disk write strategy, and switching the database standby library into a new database main library.

5. The method of restarting a database according to claim 1, wherein before stopping and restarting the database library in response to a remote procedure call request, further comprising:

and the master-slave delay of the database master library and the database slave library is less than a preset restart threshold value.

6. The method of restarting a database according to claim 1, wherein the method further comprises:

and if the master-slave delay of the database master library and the database slave library is greater than or equal to a preset restart threshold, forcibly restarting the database master library and the database slave library.

7. The method of restarting a database according to claim 1, wherein before switching the database master library to a database new backup library and switching the database backup library to a database new master library, further comprising:

and supporting delayed switching, and detecting that the current time is consistent with the specified switching time.

8. An apparatus for restarting a database, comprising:

the response module is used for responding to the remote procedure call request, and stopping and restarting the database standby library;

the transfer module is used for transferring the data request from the database main library to the database standby library under the condition that the data in the database main library and the data in the database standby library are consistent;

the switching module is used for switching the database main library into a database standby library and switching the database standby library into a database new main library;

and the restarting module is used for restarting the new standby database of the database.

9. An electronic device that reboots a database, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

10. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.

Images