Multi-master data replication in a distributed multi-tenant system

• US 10,459,908 B2
• Filed: 06/30/2016
• Issued: 10/29/2019
• Est. Priority Date: 04/11/2011
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Varley, Ian, Hansma, Scott, Burstein, Paul
• Primary Examiner(s): Hershley, Mark E
• Application Number:
  US15/198,411
• Publication Number:
  US 20160306837A1
• Time in Patent Office: 1,216 Days
• Field of Search: 707795
• CPC Class Codes: G06F 16/2322 using timestamps
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• 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: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing

Abstract

A multi-master replication system is disclosed. The multi-master replication system allows a large set of peer instances to collaboratively replicate data to each other.

Claims

1. In a replicated database by an instance of the replicated database, wherein the instance is one of a plurality of instances of the replicated database, and each replicated database instance is separately responsible for multiple database tables local to the respective replicated database instances, a method comprising:

maintaining, for each data center, a mapping of which replicated database instances are leader instances and which replicated database instances are non-leader instances, wherein the plurality of instances of the replicated database exist within two or more data centers, each data center having one leader instance and a plurality of non-leader instances, the plurality of non-leader instances to communicate with other non-leader instances of the same data center and the leader instance of the same data center and not to instances of other data centers, the leader instance to communicate with leader instances of other data centers and not with non-leader instances of other data centers, wherein each instance acts as both a client by requesting updates from all known peer instances of the plurality of instances with which it is permitted to communicate in accordance with its configuration as a leader instance or a non-leader instance as well as a server by providing its own data to other instances upon request;

maintaining, in a database table for each instance of the plurality of instances, at least information related to availability and information related to recently applied replication updates, wherein the information related to availability relates to run-time changes in a state of reachability of respective instances of the plurality of instances;

monitoring for a change to at least one record of the local database tables;

generating a chunk of information that stores metadata about record changes and corresponds to a discrete unit of progress for both change detection and transport;

serving the chunk to another instance of the replicated database via one or more leader instances to replicate the detected change to the other instance; and

synchronizing the database table in response to changes in availability or changes in recently applied replication updates.

2. The method of claim 1 further comprising:

receiving by the instance a chunk from a remote instance of the replicated database, which has metadata identifying a set of changed records for database tables of the remote instance;

in response to the receiving, requesting underlying data for changed records indicated in the received chunk via the one or more leader instances; and

upserting the changed records into the local database tables.

3. The method of claim 2, wherein the instance includes a modification timestamp indicating a most recent update of the instance, and wherein requesting the underlying data further comprises:

updating the modification timestamp with a modification timestamp of the received chunk.

4. The method of claim 2, wherein receiving the chunk further comprises:

identifying a time-based trigger to update the instance; and

requesting chunks from one or more remote instances, wherein the instance requests underlying data and upserts changed records for each received chunk.

5. The method of claim 2, wherein upserting the changed records further comprises:

inserting new records into the local database tables for records that do not exist in the local database tables; and

merging changed data into the local database tables for records that do exist in the local database tables.

6. The method of claim 2, wherein upserting the changed records further comprises:

determining if a modification timestamp of a changed row of data is more recent than a corresponding row in the local database tables; and

merging changed data into the local database tables when the modification timestamp is more recent;

otherwise, ignoring the changed data.

7. A non-transitory computer-readable medium to provide a replicated database by an instance of the replicated database, wherein the instance is one of a plurality of instances of the replicated database, and each instance is separately responsible for multiple database tables local to the respective instances, the medium having instructions stored on that, when executed by one or more processors, are configurable to cause the one or more processors to:

maintain, for each data center, a mapping of which replicated database instances are leader instances and which replicated database instances are non-leader instances, wherein the plurality of instances of the replicated database exist within two or more data centers, each data center having one leader instance and a plurality of non-leader instances, the plurality of non-leader instances to communicate with other non-leader instances of the same data center and the leader instance of the same data center and not to instances of other data centers, the leader instance to communicate with leader instances of other data centers and not with non-leader instances of other data centers, wherein each instance acts as both a client by requesting updates from all known peer instances of the plurality of instances with which it is permitted to communicate in accordance with its configuration as a leader instance or a non-leader instance as well as a server by providing its own data to other instances upon request;

maintain, in a database table for each instance of the plurality of instances, at least information related to availability and information related to recently applied replication updates, wherein the information related to availability relates to run-time changes in a state of reachability of respective instances of the plurality of instances;

monitor for a change to at least one record of the local database tables;

generate a chunk of information that stores metadata about record changes and corresponds to a discrete unit of progress for both change detection and transport;

serve the chunk to another instance of the replicated database via one or more leader instances to replicate the detected change to the other instance; and

synchronize the database table in response to changes in availability or changes in recently applied replication updates.

8. The non-transitory computer-readable medium of claim 7 further comprising instructions that, when executed by the one or more processors, are configurable to cause the one or more processors to:

receive by the instance a chunk from a remote instance of the replicated database, which has metadata identifying a set of changed records for database tables of the remote instance;

in response to the receiving, requesting underlying data for changed records indicated in the received chunk via the one or more leader instances; and

upsert the changed records into the local database tables.

9. The non-transitory computer-readable medium of claim 8, wherein the instance includes a modification timestamp indicating a most recent update of the instance, and wherein requesting the underlying data further comprises updating the modification timestamp with a modification timestamp of the received chunk.

10. The non-transitory computer-readable medium of claim 8, wherein receiving the chunk further comprises identifying a time-based trigger to update the instance and requesting chunks from one or more remote instances, wherein the instance requests underlying data and upserts changed records for each received chunk.

11. The non-transitory computer-readable medium of claim 8, wherein upserting the changed records further comprises inserting new records into the local database tables for records that do not exist in the local database tables and merging changed data into the local database tables for records that do exist in the local database tables.

12. The non-transitory computer-readable medium of claim 8, wherein upserting the changed records further comprises determining if a modification timestamp of a changed row of data is more recent than a corresponding row in the local database tables, and merging changed data into the local database tables when the modification timestamp is more recent, otherwise, ignoring the changed data.

13. A system to provide a replicated database by an instance of the replicated database, wherein the instance is one of a plurality of instances of the replicated database, and each instance is separately responsible for multiple database tables local to the respective instances, the medium having instructions stored on that, when executed by one or more processors, the system comprising:

at least one memory device;

one or more processors coupled with the at least one memory device, the one or more processors configurable to maintain, for each data center, a mapping of which replicated database instances are leader instances and which replicated database instances are non-leader instances, wherein the plurality of instances of the replicated database exist within two or more data centers, each data center having one leader instance and a plurality of non-leader instances, the plurality of non-leader instances to communicate with other non-leader instances of the same data center and the leader instance of the same data center and not to instances of other data centers, the leader instance to communicate with leader instances of other data centers and not with non-leader instances of other data centers, wherein each instance acts as both a client by requesting updates from all known peer instances of the plurality of instances with which it is permitted to communicate in accordance with its configuration as a leader instance or a non-leader instance as well as a server by providing its own data to other instances upon request, to maintain, in a database table for each instance of the plurality of instances, at least information related to availability and information related to recently applied replication updates, wherein the information related to availability relates to run-time changes in a state of reachability of respective instances of the plurality of instances, to monitor for a change to at least one record of the local database tables, to generate a chunk of information that stores metadata about record changes and corresponds to a discrete unit of progress for both change detection and transport, to serve the chunk to another instance of the replicated database via one or more leader instances to replicate the detected change to the other instance; and

to synchronize the database table in response to changes in availability or changes in recently applied replication updates.

14. The system of claim 13, wherein the one or more processors are further configurable to receive by the instance a chunk from a remote instance of the replicated database, which has metadata identifying a set of changed records for database tables of the remote instance, in response to the receiving, requesting underlying data for changed records indicated in the received chunk via the one or more leader instances, and to upsert the changed records into the local database tables.

15. The system of claim 14, wherein the instance includes a modification timestamp indicating a most recent update of the instance, and wherein requesting the underlying data further comprises updating the modification timestamp with a modification timestamp of the received chunk.

16. The system of claim 14, wherein receiving the chunk further comprises identifying a time-based trigger to update the instance and requesting chunks from one or more remote instances, wherein the instance requests underlying data and upserts changed records for each received chunk.

17. The system of claim 14, wherein upserting the changed records further comprises inserting new records into the local database tables for records that do not exist in the local database tables and merging changed data into the local database tables for records that do exist in the local database tables.

18. The system of claim 14, wherein upserting the changed records further comprises determining if a modification timestamp of a changed row of data is more recent than a corresponding row in the local database tables, and merging changed data into the local database tables when the modification timestamp is more recent, otherwise, ignoring the changed data.