Database replication

• US 9,002,793 B1
• Filed: 10/05/2012
• Issued: 04/07/2015
• Est. Priority Date: 10/05/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Ashcraft, Kenneth M, Leon, Jean-Michel, Kasera, Vishal, Agarwal, Amit
• Primary Examiner(s): LE, DEBBIE M
• Application Number:
  US13/645,989
• Time in Patent Office: 914 Days
• Field of Search: 707/636, 707/637
• US Class Current: 707/636
• CPC Class Codes: G06F 12/0806 Multiuser, multiprocessor or multiprocessing cache systems
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: H04L 49/9005 using dynamic buffer space allocation
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A write request is received at a database server from a client application for writing data to persistent data storage. In response to receiving the write request, the database server selects a set of multiple replication servers. The data is sent from the database server to the selected set of multiple replication servers for writing to the persistent data storage. Confirmation is received at the database server from replication servers in the selected set of multiple replication servers. In response to receiving confirmation from the replication servers in the selected set of multiple replication servers, the database server sends to the client application information indicating success of the write request.

Claims

1. A method comprising:

receiving, at a database server, a write request from a client application for writing data to persistent data storage;

in response to receiving the write request, selecting, by the database server, a set of multiple replication servers;

sending the data from the database server to the selected set of multiple replication servers for writing to the persistent data storage;

receiving, at the database server, confirmation from less than all of the replication servers in the selected set of multiple replication servers; and

in response to receiving confirmation from the replication servers in the selected set of multiple replication servers, selecting, by the database server, one or more additional replication servers as replacement for the replication servers from which confirmation is not received; and

sending the data from the database server to the additional replication servers.

2. The method of claim 1, wherein selecting the set of multiple replication servers in response to receiving the write request comprises:

determining, by the database server, that a mastership is acquired by the database server for servicing the write request; and

in response to determining that a mastership is acquired, selecting, by the database server, the set of multiple replication servers.

3. The method of claim 2, wherein the mastership indicates a lease on persistent data storage by an instance of the database server that is configured for servicing the write request from the client application.

4. The method of claim 1, wherein selecting the set of multiple replication servers comprises:

selecting the set of multiple replication servers from an available pool of replication servers based on a random selection mechanism.

5. The method of claim 1, wherein selecting the set of multiple replication servers comprises:

determining a level of quality guarantee that is provided to a user associated with the client application; and

selecting the set of multiple replication servers in geographically distributed locations based on the determined level of quality guarantee.

6. The method of claim 5, wherein the level of quality guarantee is based on different price structures, the quality guarantee including at least one of a lower bound on data durability and an upper bound on latency experienced in using the database server.

7. The method of claim 1, wherein selecting the set of multiple replication servers comprises:

determining an attribute chosen by a user associated with the client application, the attribute selected from the group consisting of a number of replication servers, location of replication servers, size of cache in each replication server used for the client application, location of the persistent data storage and size of the persistent data storage; and

selecting the set of multiple replication servers based on the determined attribute.

8. The method of claim 1, wherein selecting the set of multiple replication servers comprises:

performing the selection of the set of multiple replication servers independently for each write request.

9. The method of claim 1, further comprising:

receiving, at the database server, confirmation from the one or more additional replication servers; and

in response to receiving confirmation from the one or more additional replication servers, sending from the database server to the client application, information indicating success of the write request.

10. The method of claim 1, wherein replication servers in the selected set of multiple replication servers are geographically distributed.

11. A computer program product, suitably embodied in a non-transitory machine-readable medium and including instructions executable by a processor, the instructions configured to cause the processor to perform operations comprising:

receiving, at a database server, a write request from a client application for writing data to persistent data storage;

in response to receiving the write request, selecting, by the database server, a set of multiple replication servers;

sending the data from the database server to the selected set of multiple replication servers for writing to the persistent data storage;

receiving, at the database server, confirmation from less than all of the replication servers in the selected set of multiple replication servers; and

in response to receiving confirmation from the replication servers in the selected set of multiple replication servers, selecting, by the database server, one or more additional replication servers as replacement for the replication servers from which confirmation is not received; and

sending the data from the database server to the additional replication servers.

12. The computer program product of claim 11, wherein the instructions that are configured to cause the processor to perform operations comprising selecting the set of multiple replication servers in response to receiving the write request includes instructions that are configured to cause the processor to perform operations comprising:

determining, by the database server, that a mastership is acquired by the database server for servicing the write request; and

in response to determining that a mastership is acquired, selecting, by the database server, the set of multiple replication servers.

13. The computer program product of claim 12, wherein the mastership indicates a lease on persistent data storage by an instance of the database server that is configured for servicing the write request from the client application.

14. The computer program product of claim 11, wherein the instructions that are configured to cause the processor to perform operations comprising selecting the set of multiple replication servers includes instructions that are configured to cause the processor to perform operations comprising:

selecting the set of multiple replication servers from an available pool of replication servers based on a random selection mechanism.

15. The computer program product of claim 11, wherein the instructions that are configured to cause the processor to perform operations comprising selecting the set of multiple replication servers includes instructions that are configured to cause the processor to perform operations comprising:

determining a level of quality guarantee that is provided to a user associated with the client application; and

selecting the set of multiple replication servers in geographically distributed locations based on the determined level of quality guarantee.

16. The computer program product of claim 15, wherein the level of quality guarantee is based on different price structures, the quality guarantee including at least one of a lower bound on data durability and an upper bound on latency experienced in using the database server.

17. The computer program product of claim 11, wherein the instructions that are configured to cause the processor to perform operations comprising selecting the set of multiple replication servers includes instructions that are configured to cause the processor to perform operations comprising:

determining an attribute chosen by a user associated with the client application, the attribute selected from the group consisting of a number of replication servers, location of replication servers, size of cache in each replication server used for the client application, location of the persistent data storage and size of the persistent data storage; and

selecting the set of multiple replication servers based on the determined attribute.

18. The computer program product of claim 11, wherein the instructions that are configured to cause the processor to perform operations comprising selecting the set of multiple replication servers includes instructions that are configured to cause the processor to perform operations comprising:

performing the selection of the set of multiple replication servers independently for each write request.

19. The computer program product of claim 11, further including instructions that are configured to cause the processor to perform operations comprising:

receiving, at the database server, confirmation from the one or more additional replication servers; and

in response to receiving confirmation from the one or more additional replication servers, sending from the database server to the client application, information to the client application indicating success of the write request.

20. The computer program product of claim 11, wherein replication servers in the selected set of multiple replication servers are geographically distributed.