Update dependency control for multi-master replication

• US 7,584,174 B2
• Filed: 04/30/2004
• Issued: 09/01/2009
• Est. Priority Date: 05/15/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Blanco, Marcos Ares, Reveane, Joseph
• Primary Examiner(s): Lee; Wilson
• Application Number:
  US10/835,977
• Publication Number:
  US 20040230619A1
• Time in Patent Office: 1,950 Days
• Field of Search: 707 1- 10
• US Class Current: 1/1
• 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/275 Synchronous replication
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

The invention proposes a directory server system having a master server and a non-master server, each server being capable of storing directory server data comprising updates. The master server is capable of sending selected updates to the non-master server, and the non-master server (512) has:

• • a dependency checker (5224) operable for determining whether each update received from the master server (510) depends on other updates among the selected updates, and if not for sending the update to an update application function (5220),
  • the update application function being operable for applying the updates received from the dependency checker in the non-master server directory server data.

Claims

1. A directory server system having a master server and a non-master server, wherein each server is configured to store directory server data comprising updates;

said master server configured to;

determine selected updates to the directory server data to send to the non-master server;

send the selected updates to the non-master server asynchronously, wherein sending the updates asynchronously comprises sending each update to the non-master server without waiting for confirmation from the non-master server that previously sent updates have been completed at the non-master server;

said non-master server having;

a dependency checker operable for determining whether each update received from the master server depends on other updates among the selected updates, and if not for sending the update to an update application function,

the update application function being operable for applying the updates received from the dependency checker in the non-master server directory server data;

wherein the master server and the non-master server are both servers for the directory server data.

2. The directory server system of claim 1, wherein the dependency checker is responsive to the update depending on other updates among the selected updates for further determining whether said all the other updates have been applied to the non-master directory server data, and if not for adding an item representing said update in pending update items.

3. The directory server system as claimed in claim 2, wherein the update application function is further operable, upon applying an update to the non-master directory server data, for adding an item representing that update in update application state items.

4. The directory server system of claim 3, wherein the dependency checker is operable for determining whether said other updates have been applied to the non-master directory server data by scanning the update application state items.

5. The directory server system as claimed in claim 2, wherein the dependency checker is further responsive to said other updates being applied to the non-master directory server data, for sending said update to the update application function.

6. The directory server system as claimed in claim 1, wherein the update application function is further operable, upon applying an update to the non-master directory server data, for sending to the master server an acknowledgment indication representing that update.

7. The directory server system as claimed in claim 2, wherein the update application function is further operable, upon applying an update, for sequentially invoking the dependency checker for each update represented in the pending update items.

8. The directory server system as claimed in claim 1, wherein the master server has:

a dependency builder capable of computing dependency indications for each update among the selected updates, each dependency indication representing an update among the selected updates on which said update depends,

a sender for sending the selected updates to the non-master server, together with their respective dependency indications.

9. The directory server system of claim 8, wherein the dependency checker is operable for determining whether each update received from the master server depends on other updates among the selected updates, by scanning the dependency indications attached to said update.

10. The directory server system as claimed in claim 8, wherein each update has a creation time attached thereto indicating the time at which the update was locally created, and the master server has:

an update log for storing a history of the updates applied to its directory server data, according to the creation times of the updates,

the master server being capable of successively selecting the updates to be sent to the non-master from the update log.

11. The directory server system as claimed in claim 10, wherein the dependency builder has:

a two input array, said array being filled based on predefined dependency links between existing update types and being responsive to a first update being inputted at a first input and a second update being inputted at a second input for providing a dependency value indicating the dependency link of the first update with respect to the second update, the dependency builder being capable of computing the dependency indications for a selected update from said two input array.

12. The directory server system as claimed in claim 11, wherein the master server maintains update sending state items, each item representing an update among the selected updates which have been previously sent to the non-master, the dependency builder being capable of computing the dependency indications for a selected update by scanning the update sending state items.

13. The directory server system of claim 12, wherein the master server has an acknowledgment indication storage for storing the acknowledgment indications received from the non-master, and

the update sending state items represents the updates which are not represented in an acknowledgment indication storage among the selected updates which have been previously sent to the non-master.

14. The directory server system of claim 12, wherein the dependency builder is capable of:

scanning the update sending state items, upon selection of an update, and for each update sending state item being scanned,

inputting the selected update at the first input of the two input array and the update represented by said update sending state item at the second input of the two input array, and

determining whether the dependency value provided by the two input array indicate that the selected update depends on the update represented by the update sending state item, and if so adding a representation of that update in the dependency indications.

15. The directory server system as claimed in claim 11, wherein the master server is further capable of attaching ordering indications to the updates selected from the update log, the sender being further capable of sending the ordering indication attached to a selected update together with that update.

16. The directory server system of claim 15, wherein said ordering indications comprise ordering numbers being increasingly attached to the selected updates.

17. The directory server system as claimed in claim 15, wherein each item representing an update in the update sending state items comprises the ordering indication attached to that update.

18. The directory server system of claim 15, wherein the acknowledgement indication sent by the update application function upon applying an update to the non-master directory server data comprises the ordering indication attached to that update.

19. The directory server system as claimed in claim 15, wherein each dependency indication representing an update in the update sending state items comprises the ordering indication attached to that update.

20. The directory server system as claimed in claim 15, wherein the non-master server comprises an incoming update storage for storing the updates received from the master server, said incoming update storage being ordered according to the ordering indications attached to the received updates, and the dependency checker is operable for selecting the update having the lowest ordering indication among the updates in the incoming update storage.

21. The directory server system as claimed in claim 14, wherein the update application state items are ordered according to the ordering indications attached to the updates.

22. The directory server system as claimed in claim 14, wherein the pending update storage is ordered according to the ordering indications attached to the received updates.

23. A method of operating a directory server system, having a master server and a non-master server, each server configured to store directory server data comprising updates,

the method comprising said master server:

determining selected updates to the directory server data to send to the non-master server;

sending the selected updates to the non-master server asynchronously, wherein sending the updates asynchronously comprises sending each update to the non-master server without waiting for confirmation from the non-master server that previously sent updates have been completed at the non-master server; and

said non-master server;

a) determining, by a dependency checker of the non-master server, whether each update received by the non-master server from the master server depends on other updates among the selected updates, and in response to determining that it does not, the dependency checker sending the update to an update application function of the non-master server;

b) applying, by the update application function of the non-master server, the update received from the dependency checker in the non-master server directory server data;

wherein the master server and the non-master server are both sewers for the directory sewer data.

24. The method of claim 23, further comprising the steps of:

c) if step a) succeeds, determining whether all the other updates on which the update depends have been applied to the non-master directory sewer data, and if step c) fails,

d) adding an item representing said update in pending update items.

25. The method of claim 24, wherein step b) further comprises adding an item representing that update in update application state items.

26. The method of claim 25, wherein step c) comprises scanning the update application state items.

27. The method as claimed in claim 24, further comprising performing step b) if step c) succeeds.

28. The method as claimed in claim 23, wherein step b) comprises the further step of transmitting an acknowledgment indication representing the update applied from the non-master server to the master server.

29. The method as claimed in claim 23, wherein step b) comprises the further step of iteratively repeating steps a) and b) for each update represented in the pending update items, upon applying the update.

30. The method as claimed in claim 28, comprising the previous steps of:

i) computing dependency indications, in the master server, for each update among the selected updates, each dependency indication representing an update among the selected updates on which said update depends,

ii) transmitting the selected updates from the master server to the non-master server, together with their respective dependency indications.

31. The method of claim 30, wherein step a) comprises scanning the dependency indications attached to the update.

32. The method as claimed in claim 30, in which the master server has a two input array, said array being filled based on predefined dependency links between existing update types and being responsive to a first update being inputted at a first input and a second update being inputted at a second input for providing a dependency value indicating the dependency link of the first update with respect to the second update, wherein step i) comprises computing the dependency indications for a selected update from said two input array.

33. The method as claimed in claim 32, in which the master sewer maintains update sending state items, each item representing an update among the selected updates which have been previously sent to the non-master,

wherein step i) comprises computing the dependency indications for a selected update by scanning the update sending state items.

34. The method as claimed in claim 30, in which the master server maintains:

an acknowledgment indication storage for storing the acknowledgment indications received from the non-master, and

update sending state items, each item representing an update among the selected updates which have been previously sent to the non-master and which are not represented in the acknowledgment indication storage,

wherein step i) comprises computing the dependency indications for a selected update by scanning the update sending state items.

35. The method of claim 33, wherein step i) comprises the steps of:

i1) scanning the update sending state items, upon selection of an update, and for each update sending state item being scanned,

i2) inputting the selected update at the first input of the two input array and the update represented by said update sending state item at the second input of the two input array, and

i3) determining whether the dependency value provided by the two input array indicate that the selected update depends on the update represented by the update sending state item, and if so adding a representation of that update in the dependency indications.

36. The method as claimed in claim 33, in which each update has a creation time attached thereto indicating the time at which the update was locally created, and the master server has an update log for storing a history of the updates applied to its directory server data, according to the creation times of the updates,

the master server being capable of successively selecting the updates to be sent to the non-master from the update log, wherein:

step i) comprises the previous step of attaching ordering indications to the updates selected from the update log, in the master server, and step ii) comprises transmitting the ordering indication attached to a selected update together with the update.

37. The method as claimed in claim 36, wherein the non-master server comprises an incoming update storage for storing the updates received from the master server, said incoming update storage being ordered according to the ordering indications attached to the received updates, wherein step a) comprises the previous step of selecting the update having the lowest ordering indication among the updates in the incoming update storage.