Database replication system

• US 8,612,385 B2
• Filed: 10/21/2008
• Issued: 12/17/2013
• Est. Priority Date: 10/21/2008
• Status: Active Grant

• Current Assignee: TiVo Solutions Inc. (Adeia Inc.)
• Original Assignee: TiVo Inc. (Adeia Inc.)
• Inventors: Schine, Gabriel
• Primary Examiner(s): Richardson, James E
• Application Number:
  US12/254,842
• Publication Number:
  US 20100114821A1
• Time in Patent Office: 1,883 Days
• Field of Search: 707/613, 707/614, 707/616, 707/620, 707/622, 707/623, 707/632, 707/692
• US Class Current: 707/614
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

A method and apparatus for updating a slave system in a multi-master replication network is provided. The method involves executing a first event on a first master system within the multi-master replication network and executing a second event on a second master system in the multi-master replication network, where the first event and the second event are identical. The method further involves selecting an event from the first event and the second event and executing the selected event on a slave system.

Claims

1. A method for executing an event in a multi-master replication network, comprising:

monitoring events executed on a first master system in a multi-master replication network and identifying occurrence of a first event executed on the first master system;

replicating the first event to a second master system in the multi-master replication network and executing the replicated first event on the second master system as a second event;

monitoring events executed on the second master system and identifying occurrence of the second event executed on the second master system;

determining the first event and the second event to be identical;

selecting, by a slave system, a first occurring event of the first event and the second event for execution on the slave system in the multi-master replication network without selecting the other event of the first event and the second event for execution on the slave system in response to determining that the first event and second event are identical, the slave system is a slave of both the first master system and the second master system, and selecting the first occurring event comprises;

designating the first master system as an originating system based on the first master system receiving a request from a client system to execute the first event, and

identifying the selected first occurring event based on the originating system; and

executing, by the slave system, the selected event.

2. The method of claim 1, further comprising:

forwarding the selected first occurring event by an intermediate system to the slave system prior to executing the selected first occurring event on the slave system.

3. The method of claim 1, wherein execution of the first event on the first master system comprises modifying a first data repository associated with the first master system, wherein execution of the second event on the second master system comprises modifying a second data repository associated with the second master system, and wherein executing the selected first occurring event on the slave system comprises modifying a third data repository associated with the slave system.

4. The method of claim 3, wherein the slave system receives the selected first occurring event using a MySQL protocol.

5. The method of claim 4, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.

6. An apparatus for executing an event in a multi-master replication network comprising:

one or more subsystems implemented at least partially in hardware, configured to monitor events executed on a first master system in a multi-master network and identify occurrence of a first event executed on the first master system;

one or more subsystems implemented at least partially in hardware, configured to replicate the first event to a second master system in the multi-master replication network and execute the replicated first event on the second master system as a second event;

one or more subsystems implemented at least partially in hardware, configured to monitor events executed on the second master system and identify occurrence of the second event executed on the second master system;

one or more subsystems implemented at least partially in hardware, configured to determine the first event and the second event to be identical;

one or more subsystems implemented at least partially in hardware, configured to select, by a slave system, a first occurring event of the first event and the second event for execution on the slave system without selecting the other event of the first event and the second event for execution on the slave system in response to determination that the first event and the second event are identical, the slave system is a slave of both the first master system and the second master system, and selection of the first occurring event comprises;

one or more subsystems implemented at least partially in hardware, configured to designate the first master system as an originating system based on the first master system receiving a request from a client system to execute the first event, and

one or more subsystems implemented at least partially in hardware, configured to identify the selected first occurring event based on the originating system; and

one or more subsystems implemented at least partially in hardware, configured to execute, by the slave system, the selected event.

7. The apparatus of claim 6, further comprising:

one or more subsystems implemented at least partially in hardware, configured to forward the selected first occurring event to the slave system prior to the slave system executing the selected first occurring event.

8. The apparatus of claim 6, wherein execution of the first event by the first master system comprises modifying a first data repository associated with the first master system, wherein execution of the second event by the second master system comprises modifying a second data repository associated with the second master system, and wherein execution of the selected first occurring event by the slave system comprises modifying a third data repository associated with the slave system.

9. The apparatus of claim 8, wherein the slave system obtains the selected first occurring event using a MySQL protocol.

10. The apparatus of claim 9, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.

11. A non-transitory computer readable medium storing software instructions for executing an event in a multi-master replication network, the software instructions comprising:

monitoring events executed on a first master system in a multi-master replication network and identifying occurrence of a first event executed on the first master system;

replicating the first event to a second master system in the multi-master replication network and executing the replicated first event on the second master system as a second event;

monitoring events executed on the second master system and identifying occurrence of the second event executed on the second master system;

determining the first event and the second event to be identical;

selecting, by a slave system, a first occurring event of the first event and the second event for execution on the slave system in the multi-master replication network without selecting the other event of the first event and the second event for execution on the slave system in response to determining that the first event and second event are identical, the slave system is a slave of both the first master system and the second master system, and selecting the first occurring event comprises;

designating the first master system as an originating system based on the first master system receiving a request from a client system to execute the first event, and

identifying the selected first occurring event based on the originating system; and

executing, by the slave system, the selected event.

12. The non-transitory computer readable medium of claim 11, wherein the instructions further comprises:

forwarding the selected first occurring event by an intermediate system to the slave system prior to executing the selected first occurring event on the slave system.

13. The non-transitory computer readable medium of claim 11, wherein execution of the first event on the first master system comprises modifying a first data repository associated with the first master system, wherein execution of the second event on the second master system comprises modifying a second data repository associated with the second master system, and wherein executing the selected first occurring event on the slave system comprises modifying a third data repository associated with the slave system.

14. The non-transitory computer readable medium of claim 13, wherein the slave system receives the selected first occurring event using a MySQL protocol.

15. The non-transitory computer readable medium of claim 14, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.