High availability lightweight directory access protocol service

• US 7,107,355 B2
• Filed: 02/11/2002
• Issued: 09/12/2006
• Est. Priority Date: 02/11/2002
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Gammo, Louay, Herrmann, Frederic E., Bethmangalkar, Ramachandra
• Primary Examiner(s): Cardone, Jason
• Assistant Examiner(s): Patel, Chirag R
• Application Number:
  US10/074,763
• Publication Number:
  US 20030154305A1
• Time in Patent Office: 1,674 Days
• Field of Search: 709/203, 709/245, 707/203, 707/204, 714/100
• US Class Current: 709/245
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Management of lightweight directory access protocol (LDAP) service may be accomplished through the use of remote mirroring and a unique application program interface (API). Both a primary and a secondary LDAP server are maintained. Any modification to the primary LDAP server is then mirrored on the secondary LDAP server. When a call is attempted on the primary server, if it fails, the call is retried on the secondary LDAP server. The API allows for specialized grammar for commands that permits the system to handle primary (and secondary) LDAP server failure.

Claims

1. A method implemented by a secondary server to maintain a secondary directory, comprising:

receiving notification from a primary server that a particular non-idempotent operation has been performed by the primary server on a primary directory;

in response to the notification, performing the particular non-idempotent operation on the secondary directory such that the secondary directory mirrors the primary directory;

receiving a request, from a client, to perform the particular non-idempotent operation on the secondary directory, wherein the client sends the request because the client has not received confirmation that the primary server has performed the particular non-idempotent operation on the primary directory;

recognizing that the particular non-idempotent operation, identified in the request, cannot be performed on the secondary directory because the particular non-idempotent operation has already been performed on the secondary directory as a result of receiving the notification from the primary server; and

in response to the recognition that the particular non-idempotent operation has already been performed on the secondary directory, the secondary server sending an indication to the client that the particular non-idempotent operation was successfully performed on the secondary directory even though the non-idempotent operation was not performed on the secondary directory after receiving the request.

2. The method of claim 1, wherein said particular non-idempotent operation is an add operation.

3. The method of claim 1, wherein said particular non-idempotent operation is a delete operation.

4. The method of claim 1, wherein said particular non-idempotent operation is a rename operation.

13. The method of claim 1, wherein said primary directory and said secondary directory are both LDAP directories.

5. A machine-readable medium carrying one or more sequences of instructions for maintaining a secondary directory, wherein execution of the one or more sequences of instructions by one or more processors of a secondary server causes the one or more processors to perform the steps of:

receiving notification from a primary server that a particular non-idempotent operation has been performed by the primary server on a primary directory;

in response to the notification, performing the particular non-idempotent operation on the secondary directory such that the secondary directory mirrors the primary directory;

receiving a request, from a client, to perform the particular non-idempotent operation on the secondary directory, wherein the client sends the request because the client has not received confirmation that the primary server has performed the particular non-idempotent operation on the primary directory;

recognizing that the particular non-idempotent operation, identified in the request, cannot be performed on the secondary directory because the particular non-idempotent operation has already been performed on the secondary directory as a result of receiving the notification from the primary server; and

in response to the recognition that the particular non-idempotent operation has already been performed on the secondary directory, the secondary server sending an indication to the client that the particular non-idempotent operation was successfully performed on the secondary directory even though the non-idempotent operation was not performed on the secondary directory after receiving the request.

6. The machine-readable medium of claim 5, wherein said particular non-idempotent operation is an add operation.

7. The machine-readable medium of claim 5, wherein said particular non-idempotent operation is a delete operation.

8. The machine-readable medium of claim 5, wherein said particular non-idempotent operation is a rename operation.

14. The machine-readable medium of claim 5, wherein said primary directory and said secondary directory are both LDAP directories.

9. An apparatus for maintaining a secondary directory, comprising:

means for receiving notification from a primary server that a particular non-idempotent operation has been performed by the primary server on a primary directory;

means for performing the particular non-idempotent operation on a secondary directory such that the secondary directory mirrors the primary directory in response to receiving the notification;

means for receiving a request, from a client, to perform the particular non-idempotent operation on the secondary directory, wherein the client sends the request because the client has not received confirmation that the primary server has performed the particular non-idempotent operation on the primary directory;

means for recognizing that the particular non-idempotent operation, identified in the request, cannot be performed on the secondary directory because the particular non-idempotent operation has already been performed on the secondary directory as a result of receiving the notification from the primary server; and

means for sending, from the secondary server, an indication to the client that the particular non-idempotent operation was successfully performed on the secondary directory in response to the recognition that the particular non-idempotent operation has already been performed on the secondary directory even though the non-idempotent operation was not performed on the secondary directory after receiving the request.

10. The apparatus of claim 9, wherein said particular non-idempotent operation is an add operation.

11. The apparatus of claim 9, wherein said particular non-idempotent operation is a delete operation.

12. The apparatus of claim 9, wherein said particular non-idempotent operation is a rename operation.

15. The apparatus of claim 9, wherein said primary directory and said secondary directory are both LDAP directories.