Provisional authority in a distributed database

• US 8,250,030 B2
• Filed: 09/21/2005
• Issued: 08/21/2012
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: Infoblox Incorporated
• Original Assignee: Infoblox Incorporated
• Inventors: Bailey, Stuart M., Pulleyn, Ivan W., Gutti, Srinath
• Primary Examiner(s): Mahmoudi, Tony
• Assistant Examiner(s): CHOI, MICHELE C
• Application Number:
  US11/232,438
• Publication Number:
  US 20070067302A1
• Time in Patent Office: 2,526 Days
• Field of Search: 707/1, 707/8, 707/9, 707/10, 707/100, 707/102, 707/200, 707/201, 707/202, 707/203, 707/204, 707/205
• US Class Current: 707/623
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• 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 61/2521 Translation architectures other than single NAT servers
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5046 Resolving address allocation conflicts; Testing of addresses testing when self-assigning an address H04L61/5092

Abstract

Techniques for writing data in a distributed database system having a plurality of members and a master are disclosed. In one embodiment, a write request is received at an originating member. The write request is applied to a version of a database on the originating member and is placed in a journal queue of items for propagating to the master in one single atomic action. The write request is propagated to the master. Whether the propagated write request is associated with a conflict is determined, and in an event it is determined that the propagated write request is associated with the conflict, an indication that the write request is associated with the conflict is sent to the originating member.

Claims

1. A computer-implemented method of writing data in a self-adaptive distributed database system having a plurality of members and a master, including:

receiving a write request comprising a set of computer instructions at an originating member, wherein the originating member stores a local copy of a Dynamic Host Control Protocol (DHCP) database, and wherein the write request includes associating a first IP address allocated using Dynamic Host Control Protocol (DHCP) with a first device on a first network;

applying the received write request comprising the set of computer instructions to a version of a database on the originating member for provisionally writing data in the version of the database on the originating member and placing the received write request comprising the set of computer instructions in a journal queue of items for propagating to the master, wherein the applying the write request to the version of the database on the originating member and the placing the write request in the journal queue of items for propagating to the master are performed within a same single atomic transaction;

propagating the write request to the master, wherein the master stores a master copy of the DHCP database;

determining, using a processor, whether the propagated write request is associated with a conflict, wherein the conflict includes determining that the first IP address is associated with both the first device and a second device on the first network thereby resulting in an IP address allocation conflict on the first network; and

in an event it is determined that the propagated write request is associated with the conflict, sending to the originating member an indication that the write request is associated with the conflict, wherein a router uses network address translation (NAT) to map a second IP address to the first IP address for routing communications to the first device so that the first device does not need to obtain a new IP address allocation using the DHCP until the first device renews a DHCP lease.

2. The computer-implemented method as recited in claim 1, wherein the write request is expressed as a semantic command.

3. The computer-implemented method as recited in claim 1, further including writing to a version of a database on the master.

4. The computer-implemented method as recited in claim 1, further including reversing a write to the originating member.

5. The computer-implemented method as recited in claim 1, further including confirming that a write to the originating member was reconciled with the master.

6. The computer-implemented method as recited in claim 1, further including removing the write request from the journal queue.

7. The computer-implemented method as recited in claim 1, wherein the write request is associated with one or more operations to define an atomic transaction.

8. The computer-implemented method as recited in claim 1, wherein the write request is associated with one or more operations to define an atomic transaction, wherein the atomic transaction includes writing to a version of the database on an active node of the originating member and writing to a version of the database on a passive node of the originating member.

9. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions, which, when executed, cause a computer to:

receive a write request comprising a set of computer instructions at an originating member, wherein the originating member stores a local copy of a Dynamic Host Control Protocol (DHCP) database, and wherein the write request includes associating a first IP address allocated using Dynamic Host Control Protocol (DHCP) with a first device on a first network;

apply the write request comprising the set of computer instructions to a version of a database on the originating member for provisionally writing data in the version of the database on the originating member and place the write request in a journal queue of items for propagating to a master, wherein the applying the received write request to the version of the database on the originating member and the placing the received write request comprising the set of computer instructions in the journal queue of items for propagating to the master are performed within a same single atomic transaction;

propagate the write request to the master, wherein the master stores a master copy of the DHCP database;

determine whether the propagated write request is associated with a conflict, wherein the conflict includes determining that the first IP address is associated with both the first device and a second device on the first network thereby resulting in an IP address allocation conflict on the first network; and

in an event it is determined that the propagated write request is associated with the conflict, sending to the originating member an indication that the write request is associated with the conflict, wherein a router uses network address translation (NAT) to map a second IP address to the first IP address for routing communications to the first device so that the first device does not need to obtain a new IP address allocation using the DHCP until the first device renews a DHCP lease.

10. The computer program product as recited in claim 9, wherein the write request is expressed as a semantic command.

11. The computer program product as recited in claim 9, the computer program product further comprising computer instructions which, when executed, cause the computer to write to a version of a database on the master.

12. The computer program product as recited in claim 9, the computer program product further comprising computer instructions which, when executed, cause the computer to reverse a write to the originating member.

13. The computer program product as recited in claim 9, the computer program product further comprising computer instructions which, when executed, cause the computer to confirm that a write to the originating member was reconciled with the master.

14. The computer program product as recited in claim 9, the computer program product further comprising computer instructions which, when executed, cause the computer to remove the write request from the journal queue.

15. The computer program product as recited in claim 9, wherein the write request is associated with one or more operations to define an atomic transaction.

16. The computer program product as recited in claim 9, wherein the write request is associated with one or more operations to define an atomic transaction, wherein the atomic transaction includes writing to the version of the database on the originating member and writing to the journal queue.

17. The computer program product as recited in claim 9, wherein the write request is associated with one or more operations to define an atomic transaction, wherein the atomic transaction includes writing to a version of the database on an active node of the originating member and writing to a version of the database on a passive node of the originating member.

18. A system having a plurality of members and a master, including a memory coupled with a processor, wherein the memory provides the processor with instructions configured to perform steps of:

receiving a write request comprising a set of computer instructions at an originating member, wherein the originating member stores a local copy of a Dynamic Host Control Protocol (DHCP) database, and wherein the write request includes associating a first IP address allocated using Dynamic Host Control Protocol (DHCP) with a first device on a first network;

applying the received write request comprising the set of computer instructions to a version of a database on the originating member for provisionally writing data in the version of the database on the originating member and placing the write request in a journal queue of items for propagating to the master, wherein the applying the received write request comprising the set of computer instructions to the version of the database on the originating member and the placing the write request in the journal queue of items for propagating to the master are performed within a same single atomic transaction;

propagating the write request to the master, wherein the master stores a master copy of the DHCP database;

determining at the master whether the propagated write request is associated with a conflict, wherein the conflict includes determining that the first IP address is associated with both the first device and a second device on the first network thereby resulting in an IP address allocation conflict on the first network; and

in an event it is determined that the propagated write request is associated with the conflict, sending to the originating member an indication that the write request is associated with the conflict, wherein a router uses network address translation (NAT) to map a second IP address to the first IP address for routing communications to the first device so that the first device does not need to obtain a new IP address allocation using the DHCP until the first device renews a DHCP lease.

19. The system as recited in claim 18, wherein the write request is expressed as a semantic command.

20. The system as recited in claim 18, wherein the processor is further configured to perform a step of writing to a version of a database on the master.

21. The system as recited in claim 18, wherein the processor is further configured to perform a step of reversing a write to the originating member.

22. The system as recited in claim 18, wherein the processor is further configured to perform a step of confirming that a write to the originating member was reconciled with the master.

23. The system as recited in claim 18, wherein the processor is further configured to perform a step of removing the write request from the journal queue.

24. The system as recited in claim 18, wherein the write request is associated with one or more operations to define an atomic transaction.

25. The system as recited in claim 18, wherein the write request is associated with one or more operations to define an atomic transaction, wherein the atomic transaction includes writing to a version of the database on an active node of the originating member and writing to a version of the database on a passive node of the originating member.