JP2011221594A - System and method for multiplexing database - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and method for multiplexing a database capable of easily and simply multiplex a database without requiring any special considerations concerning data registration processing.SOLUTION: A database multiplexing system 100 having a first server 1A, a second server 1B and a server to be referred 3 which are mutually and communicably connected thereto, includes: a data acquisition section 11A for allowing the first server 1A to sequentially acquire data stored in the server to be referred 3; a data generation section 12A and a data registration section 13A for storing data generated from the acquired data in a master DB 22A; a first duplication section 14A for transmitting the stored data to a second server 1B for duplication; a second duplication section 15A for storing data received from the second server 1B in a slave DB 24A which is a replica of the second server 1B; and a consistency confirmation section 16A for confirming whether or not there is consistency between the master DB 22A and the slave DB 24A.

Description

  The present invention relates to a database multiplexing system and a multiplexing method.

  Conventionally, many methods for multiplexing databases and preparing for database failures have been shown (for example, see Patent Document 1). In the replication DB consistency check method described in Patent Document 1, all update processes for each of a master database and a replica database (slave database) are stored in an update history database owned by each, and both update history databases are stored at regular intervals. And only the difference information from the previous comparison is left in the update history database. As a result, the information remaining in the update history database becomes a difference between the master database and the replica database, and consistency is confirmed by referring to the update history database, and falsification of the replica database is detected.

JP 2005-250819 A

  However, what is described in Patent Document 1 is a database multiplexing system including one master database and one replica database, and data registration processing stops when the master database fails. Therefore, the data update to both databases stops.

  By the way, in the case of a database multiplexing system including a master database and a replica database, it is common to have a registration unit for registering data not only on the master database side but also on the replica database side. In such a system, in a normal state, the registration unit on the master database side and the registration unit on the replica database side register data in half in the master database, and then update the replica database based on the master database. When a failure occurs, all the data is registered on the database side where no failure has occurred, so that the data in the operating database can be updated without stopping all processing. However, since such a system multiplexes the registration process, it is necessary to consider the distribution of the data contents to be registered and the distribution of the database server, and the process is complicated.

  It is an object of the present invention to provide a database multiplexing system and a multiplexing method that can be multiplexed easily and simply without requiring special consideration regarding data registration processing.

  The inventors of the present invention have found that the master database and the slave database are duplicated so that no special consideration is required for processing, and the present invention has been completed. Specifically, the present invention provides the following.

  (1) A database multiplexing system in which a first server and a second server, which are two database servers, and a referenced server are connected so as to communicate with each other, wherein the first server and the second server are: A data acquisition unit that sequentially acquires data stored in the referenced server, a data registration unit that stores data acquired by the data acquisition unit in a master database included in each of the database servers, and the data registration unit A first replication unit for transmitting the stored data to the second server and the first server for replication; and data received from the second server and the first server respectively for the second server and the first server A second replicating unit for storing in a slave database that is a replica of the server, the master database, and the slave database; And a consistency confirmation unit for confirming whether consistency is taken with a database multiplexing system.

  According to such a configuration of the present invention, the database multiplexing system divides the database managed by each database server into two, that is, a master database and a slave database, for example, the database stored in the second server. Data replication (duplication) processing is unidirectional, such as having the contents replicated to the first server, so that it is possible to multiplex easily and simply without the need to distribute the processing contents at each database server it can. Therefore, since the database multiplexing system makes the processing of the first server and the second server substantially the same, the data registration processing can be simplified.

  Further, the database multiplexing system manages the data registered in the first server and the data registered in the second server in the same database server, so that the contents of the database stored in the first server, Consistency with the contents of the database stored in the second server can be easily confirmed.

  (2) The database multiplexing system according to (1), further including a data complementing unit that updates data stored in the slave database with respect to the master database when the consistency check unit determines NO. .

  According to such a configuration of the present invention, since the database multiplexing system includes the data complementing unit that updates the data stored in the slave database to the master database, for example, at the time of failure recovery of the first server, One server can be recovered by referring to the database stored in the first server. Therefore, the database multiplexing system can recover from a failure with a simple operation.

  (3) A multiplexing method using a database multiplexing system in which a first server and a second server, which are two database servers, and a referenced server are connected so as to communicate with each other, the first server, A data acquisition step in which the second server sequentially acquires the data stored in the referenced server, and the data acquired by the first server and the second server in the data acquisition step are stored in each of the database servers. A data registration step for storing in the master database provided, and the first server storing the data stored in the data registration step for storage in a slave database that is a replica of the first server provided in the second server. A first duplication step of transmitting to the second server, and the second server comprising the first server; A second replication step of storing the data received from the server in the slave database of the second server, and the second server storing the data in a slave database that is a replica of the second server included in the first server A third replication step of transmitting the data stored in the data registration step to the first server; and the slave server of the first server using the data received by the first server from the second server. A fourth replication step stored in the first database, and a consistency confirmation step for confirming whether or not the master database provided in each of the first server and the second server is consistent with the slave database. Multiplexing method including.

  According to such a configuration of the present invention, it is possible to provide a method having the same effect as (1).

  According to the present invention, it is possible to provide a database multiplexing system and a multiplexing method that allow simple and simple multiplexing without requiring special consideration regarding data registration processing.

It is a figure which shows the function structure of the whole structure of a database multiplexing system which concerns on this embodiment, and a 1st server, a 2nd server, and a referred server. It is a flowchart of the 1st server which occurs when the 1st server concerning this embodiment acquires data. It is a flowchart of the 1st server which occurs when data reception from the 2nd server concerning this embodiment occurs.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. This is merely an example, and the technical scope of the present invention is not limited to this.

(Embodiment)
[Overall Configuration of Database Multiplexing System 100 and Functional Configuration of First Server 1A, Second Server 1B, and Referenced Server 3]
FIG. 1 is a diagram showing an overall configuration of a database multiplexing system 100 according to the present embodiment and functional configurations of a first server 1A, a second server 1B, and a referenced server 3.

  The database multiplexing system 100 includes a first server 1A, a second server 1B, a referenced server 3, a reference server 5, and a communication network N. Through the communication network N, the first server 1A, the second server 1B, the referenced server 3, and the reference server 5 are communicably connected.

  The first server 1A and the second server 1B are database servers having the same configuration. The first server 1A and the second server 1B acquire the same data from the referenced server 3 and perform replication with each other. The database multiplexing system 100 multiplexes databases to perform mutual replication, and thereafter performs complementary processing between the master database and the slave database, thereby improving the reliability of the entire database multiplexing system 100. Yes. The first server 1A includes a control unit 10A and a storage unit 20A. The second server 1B includes a control unit 10B and a storage unit 20B. Note that in the following description, the components common to the first server 1A and the second server 1B will be described as, for example, the control unit 10 and the like by omitting the symbols A and B. Moreover, when not distinguishing the 1st server 1A and the 2nd server 1B, it demonstrates as the database server 1. FIG.

  The control unit 10 includes a data acquisition unit 11, a data generation unit 12, a data registration unit 13, a first replication unit 14, a second replication unit 15, a consistency confirmation unit 16, and a data complement unit 17. Prepare.

  The data acquisition unit 11 is a control unit that acquires data from the referenced server 3. The data acquisition unit 11 refers to the master DB 22 (DB: database) and transmits a data acquisition request not stored in the master DB 22 to the referenced server 3, thereby responding to the request from the referenced server 3. Get the data.

  The data generation unit 12 is a control unit that generates data to be stored in the master DB 22 from data acquired from the referenced server 3. For example, the data generation unit 12 aggregates and processes the query logs acquired from the referenced server 3 to generate ranking information for each query.

  The data registration unit 13 is a control unit that stores the data generated by the data generation unit 12 in the master DB 22. If it is the above-mentioned example, the data registration part 13 can memorize | store a click total ranking in master DB22 by memorize | storing the ranking information for every produced | generated query.

  The first replication unit 14 is a control unit that transmits data acquired from the referenced server 3 and generated by the data generation unit 12 to the counterpart database server 1 for replication. The counterpart database server 1 is the second server 1B in the case of the first replicating unit 14A, and the first server 1A in the case of the first replicating unit 14B.

  The second replication unit 15 is a control unit that receives the data transmitted by the first replication unit 14 of the counterpart database server 1 and stores the data in the slave DB 24. In the case of the second replication unit 15A, the first replication unit 14 of the counterpart database server 1 is the first replication unit 14B of the second server 1B, and in the case of the second replication unit 15B, the first server 1A. The first duplicating unit 14A.

  The consistency confirmation unit 16 is a control unit that confirms whether the master DB 22 and the slave DB 24 stored in the storage unit 20 are consistent. Whether or not consistency is obtained can be determined by confirming, for example, when data is missing, when data generation time is different, or when the aggregate value of data itself is different.

  The data complementing unit 17 controls the consistency by updating the data of the slave DB 24 to the master DB 22 when it is determined that the consistency is not obtained as a result of the confirmation by the consistency confirmation unit 16. It is.

  The storage unit 20 includes a master DB 22 and a slave DB 24.

  The master DB 22 is a main DB, and is a DB for registering data acquired from the referenced server 3 and generated by the data generation unit 12.

  The slave DB 24 is a sub DB, is a DB that receives and stores data stored in the master DB 22 of the counterpart database server 1, and is a replica of the master DB 22 of the counterpart database server 1.

  The hardware of the first server 1A and the second server 1B of the present embodiment may be configured by a general computer. For example, a general computer includes a central processing unit (CPU) as the control unit 10 and a memory (RAM, ROM), a hard disk (HDD), and an optical disk (CD, DVD, etc.) as a storage unit 20 in a network. As a communication device, various wired and wireless LAN devices, as a display device, for example, various displays such as a liquid crystal display and a plasma display, and as an input device, for example, a keyboard and a pointing device (mouse, tracking ball, etc.) are appropriately provided. These are connected by a bus line. In such a general computer, the CPU of the first server 1A controls the first server 1A and the CPU of the second server 1B centrally controls the second server 1B, respectively, and reads various programs as appropriate. By executing this, the various functions according to the present invention are realized in cooperation with the hardware described above.

  The referenced server 3 is, for example, a file server, and stores a query log used for the search. The referenced server 3 is accessed by the first server 1A and the second server 1B, and the first server 1A and the second server 1B obtain, for example, a query log stored in the referenced server 3. The referenced server 3 includes a control unit 30 that controls the entire referenced server 3 and a data storage unit 32 that stores data. The hardware of the referenced server 3 may be configured by a general computer.

  The reference server 5 is, for example, a front end server such as a moving image search server. The reference server 5 executes the query on one of the master DBs 22 of the first server 1A and the second server 1B, and acquires the processing result for the query. The reference server 5 may be, for example, a personal computer (PC) or a terminal such as a mobile phone.

  The communication network N is a communication line such as the Internet for performing communication between the first server 1A, the second server 1B, the referenced server 3, and the reference server 5. The communication network N may be wired or part or all of it may be wireless.

[Processing of the first server 1A]
Next, processing in the first server 1A will be described. FIG. 2 is a flowchart of the first server 1A that occurs when the first server 1A according to the present embodiment acquires data. FIG. 3 is a flowchart of the first server 1A that occurs when data reception from the second server 1B according to the present embodiment occurs. The second server 1B performs the same process as the first server 1A described below. Specifically, in the processing in the second server 1B, if the portion described as the second server 1B in the following description is replaced with the first server 1A, the rest is the same as the processing in the first server 1A. is there.

  S <b> 10 in FIG. 2: The control unit 10 </ b> A (data acquisition unit 11 </ b> A) acquires data from the referenced server 3. Here, the data acquisition unit 11 </ b> A may acquire data by inquiring of the referenced server 3 periodically (for example, every morning at 4 o'clock) whether or not there is update data. Further, the data acquisition unit 11A may acquire data by notifying that the referenced server 3 has been updated.

  S11: The control unit 10A (data generation unit 12A) generates data to be stored in the master DB 22A from the data acquired in S10.

  S12: The control unit 10A (data registration unit 13A) stores the data generated in S11 in the master DB 22A.

  S13: The control unit 10A (first replication unit 14A) transmits the data generated in S11 and stored in the master DB 22A in S12 to the second server 1B. Thereafter, the control unit 10A ends the process.

  S21 in FIG. 3: The control unit 10A (second replication unit 15A) receives data from the second server 1B. Here, the received data is data that the second server 1 </ b> B has acquired from the referenced server 3 and generated.

  S22: The control unit 10A (second replication unit 15A) stores the received data in the slave DB 24A.

  S23: The control unit 10A (consistency confirmation unit 16A) confirms whether data consistency is obtained between the master DB 22A and the slave DB 24A. As a result of checking, when it is determined that consistency is obtained (S23: YES), the control unit 10A ends the process. On the other hand, when it is determined that the consistency is not obtained as a result of the confirmation (S23: NO), the control unit 10A moves the process to S24.

  S24: The control unit 10A (data complementing unit 17A) updates the master DB 22A with data that exists in the slave DB 24A but does not exist in the master DB 22A so that the master DB 22A and the slave DB 24A can be consistent. To do. Thereafter, the control unit 10A ends the process.

  As described above, the database multiplexing system 100 can unidirectionally perform data replication processing by dividing the database managed by the first server 1A and the second server 1B into the master DB 22 and the slave DB 24, respectively. The processing contents in the database server 1 need not be allocated, and multiplexing can be performed easily and simply. Therefore, since the database multiplexing system 100 makes the processing of the first server 1A and the second server 1B substantially the same, the data registration processing can be simplified.

  In addition, the database multiplexing system 100 manages the data registered in the first server 1A and the data registered in the second server 1B in the first server 1A and the second server 1B, respectively. The consistency between the contents of the database stored in the first server 1A and the contents of the database stored in the second server 1B can be easily confirmed.

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

DESCRIPTION OF SYMBOLS 1 Database server 1A 1st server 1B 2nd server 3 Referenced server 5 Reference server 10, 10A, 10B, 30 Control part 11, 11A, 11B Data acquisition part 12, 12A, 12B Data generation part 13, 13A, 13B Data registration Unit 14, 14A, 14B First replication unit 15, 15A, 15B Second replication unit 16, 16A, 16B Consistency confirmation unit 17, 17A, 17B Data complementing unit 20, 20A, 20B, 32 Storage unit 22, 22A, 22B Master DB
24, 24A, 24B Slave DB
100 Database multiplexing system N Communication network

Claims (3)

A database multiplexing system in which a first server and a second server, which are two database servers, and a referenced server are connected so that they can communicate with each other,
The first server and the second server are:
A data acquisition unit for sequentially acquiring data stored in the referenced server;
A data registration unit for storing data acquired by the data acquisition unit in a master database included in each of the database servers;
A first replication unit that transmits the data stored by the data registration unit to the second server and the first server for replication;
A second replication unit that stores data received from the second server and the first server in a slave database that is a replica of the second server and the first server, respectively;
A consistency checking unit for checking whether or not the master database and the slave database are consistent;
Comprising
Database multiplexing system. A data complementing unit that updates the data stored in the slave database with respect to the master database when the consistency checking unit determines NO.
The database multiplexing system according to claim 1. A multiplexing method using a database multiplexing system in which two database servers, a first server and a second server, and a referenced server are connected so as to communicate with each other,
A data acquisition step in which the first server and the second server sequentially acquire data stored in the referenced server;
A data registration step in which the first server and the second server store the data acquired in the data acquisition step in a master database included in each of the database servers;
A first replication step in which the first server transmits the data stored in the data registration step to the second server for storage in a slave database that is a replica of the first server included in the second server. When,
A second replication step in which the second server stores the data received from the first server in the slave database of the second server;
A third replication step in which the second server transmits the data stored in the data registration step to the first server so as to be stored in a slave database that is a replica of the second server included in the first server; When,
A fourth replication step in which the first server stores the data received from the second server in the slave database of the first server;
A consistency confirmation step for confirming whether or not the master database provided by the first server and the second server are consistent with the slave database; and
including,
Multiplexing method.

Images