CN106021030A - Database system and database fault processing method and device - Google Patents

Abstract

The invention provides a database system and a database fault processing method and device. The method comprises the steps that 1, at least one slave database is set for a master database in advance; 2, original data in the master database is copied into each slave database in advance; 3, each operation of the master database is obtained in real time; 4, the operation which is the same as the operation of the master database is carried out on each slave database; 5, whether the master database breaks down or not is detected in real time, and if yes, any slave database is used for being substituted for the master database. By means of the database system and the database fault processing method and device, database reliability can be improved.

Description

A database system, a method and device for dealing with database faults

technical field

The invention relates to the field of computer technology, in particular to a database system, a method and a device for processing database faults.

Background technique

Complex systems have higher and higher requirements for database disaster recovery. Most systems have only one database. Once the database is misoperated or crashed during operation, it will affect the operation of the entire system and may even cause downtime. single point of failure.

In the prior art, when the database in the system fails, the services related to the database will stop running, the database is maintained, and the related services can only run normally after the database returns to normal.

It can be seen from the above description that the reliability of the existing database is low.

Contents of the invention

Embodiments of the present invention provide a database system, a method and a device for dealing with database faults, which can improve the reliability of the database.

In the first aspect, the embodiment of the present invention provides a method for processing database faults, including:

S1: Pre-set at least one slave database for the master database;

S2: Copy the original data in the master database to each of the slave databases in advance;

S3: Obtain each operation of the master database in real time;

S4: Execute the same operation as that of the master database on each of the slave databases;

S5: Detect in real time whether the master database fails, and if so, use any of the slave databases to replace the master database.

Further, before said S2, it also includes:

Create a replication account in the master database and grant REPLICATIONSLAVE permission to the replication account;

using the replication account to connect to the master database;

The S2, including:

Using the REPLICATION SLAVE authority of the replication account, the original data in the master database is replicated to each of the slave databases.

Further, before the S3, it also includes: opening the binary log of the master database;

It also includes: recording each operation of the main database in the binary log in real time;

The S3, including:

Obtain each operation of the primary database from the binary log in real time.

Further, the use of any of the slave databases to replace the master database includes:

An external operation on the master database is converted into an operation on a slave database replacing the master database.

In a second aspect, an embodiment of the present invention provides a device for processing database faults, including:

A setting unit is used to set at least one slave database for the master database;

a replication unit, configured to replicate the original data in the master database to each of the slave databases;

an acquisition unit, configured to acquire each operation of the master database in real time;

an execution unit, configured to perform the same operation on each of the slave databases as that of the master database;

The detection unit is configured to detect in real time whether the primary database fails, and when detecting that the primary database fails, use any of the secondary databases to replace the primary database.

Further, it also includes: a creation unit, configured to create a replication account in the master database, and grant the replication account REPLICATION SLAVE permission;

a connection unit, configured to use the replication account to connect to the master database;

The replication unit is configured to use the REPLICATION SLAVE authority of the replication account to replicate the original data in the master database to each of the slave databases.

Further, it also includes: an opening unit, configured to open the binary log of the master database;

It also includes: a recording unit, configured to record each operation of the master database in the binary log in real time;

The acquiring unit is configured to acquire each operation of the master database from the binary log in real time.

Further, when the detection unit executes the method of using any of the slave databases to replace the master database, it is used to convert external operations on the master database into operations on the slave database used to replace the master database. operate.

In a third aspect, an embodiment of the present invention provides a database system, including:

The master database, at least one slave database, and the device for handling database faults described in any one of the second aspect.

Further, the master database and the at least one slave database are deployed on different servers.

In an embodiment of the present invention, at least one slave database is set for the master database, and the original data in the master database is copied to each slave database, so that each slave database preserves the original data of the master database, and each slave database Execute the same operation as that of the master database, so that each slave database is synchronized with the master database, and the backup of the slave database to the master database is realized. When the failure of the master database is detected, any slave database is used to replace the master database. External operations are required Data in the master database can also be realized by manipulating the data in the slave database. Therefore, the failure of the master database will not affect external operations on the data in the master database, which improves the reliability of the database.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in 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 For some embodiments of the present invention, those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a flow chart of a method for dealing with database faults provided by an embodiment of the present invention;

Fig. 2 is a flow chart of another method for dealing with database faults provided by an embodiment of the present invention;

Fig. 3 is a schematic diagram of a device for processing database faults provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of another device for handling database faults provided by an embodiment of the present invention;

Fig. 5 is a schematic diagram of a database system provided by an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work belong to the protection of the present invention. scope.

As shown in Figure 1, the embodiment of the present invention provides a method for processing database faults, the method may include the following steps:

S1: Pre-set at least one slave database for the master database;

S2: Copy the original data in the master database to each of the slave databases in advance;

S3: Obtain each operation of the master database in real time;

S4: Execute the same operation as that of the master database on each of the slave databases;

S5: Detect in real time whether the master database fails, and if so, use any of the slave databases to replace the master database.

In an embodiment of the present invention, at least one slave database is set for the master database, and the original data in the master database is copied to each slave database, so that each slave database preserves the original data of the master database, and each slave database Execute the same operation as that of the master database, so that each slave database is synchronized with the master database, and the backup of the slave database to the master database is realized. When the failure of the master database is detected, any slave database is used to replace the master database. External operations are required Data in the master database can also be realized by manipulating the data in the slave database. Therefore, the failure of the master database will not affect external operations on the data in the master database, which improves the reliability of the database.

In an embodiment of the present invention, before S2, it also includes:

Create a replication account in the master database and grant REPLICATIONSLAVE permission to the replication account;

using the replication account to connect to the master database;

The S2, including:

Using the REPLICATION SLAVE authority of the replication account, the original data in the master database is replicated to each of the slave databases.

In this embodiment, because operations on the master database require corresponding permissions, in order to replicate the original data in the master database, a replication account is created to provide corresponding REPLICATIONSLAVE permissions. When connecting to the master database through a replication account, the original data in the master database can be replicated. Specifically, any slave database can use the replication account and the password of the replication account to link to the master database.

In addition, in order to avoid copying all the original data in the master database to each slave database, before step S2, it also includes: prohibiting writing operations on the master database and each slave database. This can ensure that the master database and each slave database will not write new data, and ensure that the original data in the master database can be copied to each slave database, so that the data in the master database and each slave database are the same.

In an embodiment of the present invention, before the S3, it also includes:

Open the binary log of the primary database;

It also includes: recording each operation of the main database in the binary log in real time;

The S3, including:

Obtain each operation of the primary database from the binary log in real time.

In this embodiment, enabling the binary log of the master database can be implemented by configuring the master database. In order to make the configuration take effect, the master database generally needs to be restarted. Each operation of the main database is recorded in the binary log of the main database, and the record of the operation can be recorded in the form of an event. Specifically, all DDL (Data Definition Language, Data Definition Language) and DML (Data Manipulation Language, Data Manipulation Language) of the master database are recorded in the binary log.

In addition, in order to connect the master database to any slave database, the master database can also be configured, specifically, the identifier of the slave database, for example, the address of the slave database. A similar configuration is also performed on the slave database, specifically, the identity of the master database is configured, for example: the address of the master database.

When obtaining each operation of the main database from the binary log in real time, it can be automatically obtained by setting the obtaining thread. Specifically, each operation in the binary log is obtained by polling the binary log through the obtaining thread.

When executing S4, an execution thread may be set, and each acquired operation may be executed through the execution thread. This ensures the consistency of the data in the master database and the slave database.

In an embodiment of the present invention, the use of any of the slave databases to replace the master database includes:

An external operation on the master database is converted into an operation on a slave database replacing the master database.

In this embodiment, the master database is switched to the slave database, and all the functions of the master database are implemented by the slave database. Specifically, the address of the externally accessed database may be changed from the address of the master database to the address of the slave database used to replace the master database. For example, external software A needs to operate the data of the master database. Software A needs to access the master database according to the address of the configured master database. Because the master database fails, it cannot access the master database. The database is switched, and the address of the database in the configuration of software A is changed to the address of the slave database. For software A, its operation has not changed, and access is still performed according to the address of the configured database.

Take MYSQL as an example, as shown in Figure 2, the embodiment of the present invention provides a kind of method for processing database failure, in the embodiment of the present invention, master database and slave database are all MYSQL, and this method can comprise the following steps:

Step 201: Pre-setting the slave database for the master database.

The master database and the slave database are deployed on different servers, so that when the master database cannot work normally due to the failure of the server where it is located, the slave database can also realize the backup of the master database. Avoid when the master database and the slave database are on the same server, the master database and the slave database cannot work normally due to the failure of the server. In this way, even if the server where the master database is located has a failure such as downtime, the slave database can be successfully switched so that the slave database can replace the master database.

In addition, in order to ensure the success of data replication between the master database and the slave database, and to ensure that the slave database can completely replace the master server, it is necessary to ensure that the versions of the master database and the slave database are compatible, specifically, to ensure that the version of the slave database is compatible with the master database version Same or the version of the slave database is higher than the version of the master database.

Step 202: Create a replication account in the primary database, and grant REPLICATIONSLAVE permission to the replication account.

Specifically, after the replication account has the REPLICATION SLAVE authority, the original data in the primary database can be replicated.

Step 203: use the replication account to connect to the master database.

Specifically, a replication account can be used to connect the slave database to the master database.

Step 204: Using the REPLICATION SLAVE authority of the replication account, the original data in the master database is copied to the slave database.

This process can be done from the database.

Step 205: Open the binary log of the primary database.

The corresponding information is recorded in the binary log through binary.

Step 206: Record each operation of the master database in the binary log in real time.

Step 207: Obtain each operation of the primary database from the binary log in real time.

This step can be implemented from the database. Specifically, the binary log is polled in real time to obtain records in the binary log.

Step 208: Execute the same operation as that of the master database on the slave database.

Through this step, the data of the master database and the slave database can be kept in sync, so that the slave database is called the backup of the master database.

Step 209: Detect in real time whether the master database fails, and if so, replace the master database with the slave database.

For example, application A needs to read data A in the primary database. After the primary database fails, application A directly reads data A from the secondary database. For application A, the address of the database of application A can be changed from the address of the master database to the address of the slave database to realize that the slave database replaces the master database.

Specifically, external applications that need to operate the master database are switched to operate on the slave database. This step can be realized by middleware, which converts the operation on the master database into the operation on the slave database.

In the embodiment of the present invention, the asynchronous replication function of MYSQL can be used to replicate the data of the master database to the slave database. Operations on the database in the embodiment of the present invention may include: reading, writing, deleting, modifying, querying, and the like.

The embodiment of the present invention can effectively solve the problem of a single point of failure. When there is a problem with the master database, it can be quickly switched to the slave database to ensure the normal operation of the system, which is simple and reliable.

As shown in FIG. 3 and FIG. 4 , the embodiment of the present invention provides a device for handling database faults. The device embodiments can be implemented by software, or by hardware or a combination of software and hardware. From the perspective of hardware, as shown in Figure 3, it is a hardware structural diagram of the device where the device for processing database faults provided by the embodiment of the present invention is located, except for the processor, memory, network interface, and In addition to the non-volatile memory, the device where the device in the embodiment is located may generally include other hardware, such as a forwarding chip responsible for processing packets, and the like. Taking software implementation as an example, as shown in Figure 4, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the CPU of the device where it is located. A device for processing database faults provided in this embodiment includes:

A setting unit 401, configured to set at least one slave database for the master database;

a replication unit 402, configured to replicate the original data in the master database to each of the slave databases;

An acquisition unit 403, configured to acquire each operation of the master database in real time;

an execution unit 404, configured to perform the same operation on each of the slave databases as that of the master database;

The detection unit 405 is configured to detect in real time whether the master database fails, and when it is detected that the master database fails, use any of the slave databases to replace the master database.

In an embodiment of the present invention, it further includes: a creation unit, configured to create a replication account in the master database, and grant the replication account REPLICATION SLAVE permission;

a connection unit, configured to use the replication account to connect to the primary database;

The replication unit is configured to use the REPLICATION SLAVE authority of the replication account to replicate the original data in the master database to each of the slave databases.

In an embodiment of the present invention, it also includes: an opening unit, configured to open the binary log of the master database;

It also includes: a recording unit, configured to record each operation of the master database in the binary log in real time;

The acquiring unit is configured to acquire each operation of the master database from the binary log in real time.

In an embodiment of the present invention, the detection unit is configured to convert an external operation on the master database into an operation for replacing the master database by using any of the slave databases to replace the master database. Database operations from the database.

The embodiment of the present invention provides a database system, including:

The master database, at least one slave database, and any device for handling database failures in the embodiments of the present invention.

As shown in Figure 5, a database system provided by an embodiment of the present invention includes:

The master database 501, the slave database 502, and the device 503 for processing database faults in any one of the embodiments of the present invention.

In an embodiment of the present invention, the master database and the at least one slave database are deployed on different servers.

The information exchange and execution process among the units in the above-mentioned device are based on the same concept as the method embodiment of the present invention, and the specific content can refer to the description in the method embodiment of the present invention, and will not be repeated here.

Various embodiments of the present invention have at least the following beneficial effects:

1. In the embodiment of the present invention, at least one slave database is set for the master database, and the original data in the master database is copied to each slave database, so that each slave database preserves the original data of the master database. Perform the same operations on the slave database as the master database, so that each slave database is synchronized with the master database, and the backup of the slave database to the master database is realized. When detecting the failure of the master database, any slave database is used to replace the master database. When it is necessary to operate the data of the master database, it can also be realized by manipulating the data of the slave database. Therefore, the failure of the master database will not affect the external operation of the data in the master database, which improves the reliability of the database.

2. The embodiment of the present invention can effectively solve the problem of a single point of failure. When a problem occurs in the master database, it can quickly switch to the slave database to ensure that the system is running, which is simple and reliable.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or sequence. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Those of ordinary skill in the art can understand that all or part of the steps to realize the above method embodiments can be completed by program instructions related hardware, and the aforementioned programs can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that the above descriptions are only preferred embodiments of the present invention, and are only used to illustrate the technical solution of the present invention, and are not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (10)

1. the method processing database failure, it is characterised in that including:

S1: for MDL, at least one is set from data base in advance；

S2: in advance initial data in described MDL is copied to each described from data base；

S3: obtain each operation of described MDL in real time；

S4: in each described operation that execution is identical with the operation of described MDL from data base；

S5: in real time detect whether described MDL breaks down, if it is, utilize arbitrary described from Data base replaces described MDL.

Method the most according to claim 1, it is characterised in that

Before described S2, also include:

Described MDL creates and replicates account, authorize described duplication account REPLICATION SLAVE authority；

Described duplication account is utilized to connect described MDL；

Described S2, including:

Utilize the REPLICATION SLAVE authority of described duplication account, by described MDL Central Plains Beginning data copy to each described from data base.

Method the most according to claim 1, it is characterised in that

Before described S3, also include: open the binary log of described MDL；

Also include: in described binary log, record each operation of described MDL in real time；

Described S3, including:

Each operation of described MDL is obtained in real time from described binary log.

4. according to described method arbitrary in claim 1-3, it is characterised in that

Described utilization arbitrary described replaces described MDL from data base, including:

The operation of described MDL is converted to by outside to be used for replacing described MDL from data The operation in storehouse.

5. the device processing database failure, it is characterised in that including:

Unit is set, for arranging at least one from data base for MDL；

Copied cells, each described from data base for initial data in described MDL is copied to；

Acquiring unit, for each operation of the described MDL of acquisition in real time；

Performance element, in each described operation that execution is identical with described MDL from data base；

For in real time, detector unit, detects whether described MDL breaks down, when described master being detected Data base breaks down, and utilizes and arbitrary described replaces described MDL from data base.

Device the most according to claim 5, it is characterised in that

Also include: creating unit, replicate account for creating in described MDL, authorize described multiple Account REPLICATION SLAVE authority processed；

Connect unit, be used for utilizing described duplication account to connect described MDL；

Described copied cells, for utilizing the REPLICATION SLAVE authority of described duplication account, Initial data in described MDL is copied to each described from data base.

Device the most according to claim 5, it is characterised in that

Also include: open unit, for opening the binary log of described MDL；

Also include: record unit, for recording described MDL in described binary log in real time Each operation；

Described acquiring unit, for obtaining each of described MDL in real time from described binary log Operation.

8. according to described device arbitrary in claim 5-7, it is characterised in that

Described detector unit perform described utilize arbitrary described replace described MDL from data base time, For the operation of described MDL is converted to by outside to be used for replacing described MDL from data The operation in storehouse.

9. the system of a data base, it is characterised in that including:

MDL, at least one is from data base, process data as described in arbitrary claim 5-8 The device of storehouse fault.

System the most according to claim 9, it is characterised in that including:

Described MDL with described at least one from data base dispose on a different server.