Distributed directory environment using clustered LDAP servers

• US 9,390,156 B2
• Filed: 06/29/2009
• Issued: 07/12/2016
• Est. Priority Date: 06/29/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Joshi, Chandrajit G., Shah, Romil J.
• Primary Examiner(s): HUANG, MIRANDA M
• Application Number:
  US12/493,409
• Publication Number:
  US 20100332532A1
• Time in Patent Office: 2,570 Days
• Field of Search: 707/609, 707/770, 707/953, 707/966, 707/E17.032, 707/999.01
• US Class Current: 1/1
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: H04L 67/1042 using topology management mechanisms

Abstract

The clustering of LDAP servers wherein each LDAP server is connected to the databases of all other LDAP servers in addition to its own database. This creates a mesh of highly available LDAP servers that are loosely connected to all the repositories of LDAP data in the distributed directory environment. Also broadly contemplated herein is the employment of a cluster manager for managing the cluster of LDAP servers.

Claims

1. A method for managing a lightweight directory access protocol (LDAP) server in an LDAP server cluster, the method comprising:

providing a cluster manager in the LDAP server cluster comprising a plurality of LDAP servers including a first LDAP server tightly coupled to a first database and a second LDAP server tightly coupled to a second database, wherein the cluster manager is configured to manage the LDAP server cluster, said cluster manager being configured to maintain status information for each of the plurality of LDAP servers;

maintaining a proximity list for the plurality of LDAP servers in ascending order of path length from the first database tightly coupled with said first LDAP server;

providing a connection between a proxy server and said cluster manager, and configuring the proxy server to obtain said status information from the cluster manager;

configuring the proxy server to process requests for the LDAP server cluster, wherein the proxy server is communicatively coupled with a client;

receiving, at the proxy server, a client request for data from the first database;

determining from said status information that the first LDAP server is not in a normal working state; and

selecting, by the proxy server, the second LDAP server from the LDAP server cluster to execute the client request based on said status information received from the cluster manager indicating that the first LDAP server is not in the normal working state and the proximity list;

wherein each LDAP server among the plurality of LDAP servers is at least loosely coupled with each of the plurality of databases, and is tightly coupled with a respective one of the plurality of databases. and

wherein a suffix-to-database mapping table is employed to execute the client request.

2. The method of claim 1, further comprising configuring each of the plurality of LDAP servers with a configuration information of the cluster manager.

3. The method of claim 1, further comprising configuring the cluster manager with configuration information of the plurality of LDAP servers in the LDAP server cluster.

4. The method of claim 1, further comprising;

polling each of the plurality of LDAP servers at predetermined intervals for status updates; and

updating the cluster manager if there are any current status updates that are different from any previous updates in the cluster manager;

wherein the second LDAP server is determined to be most proximate among the plurality of LDAP servers in the normal working state.

5. The method of claim 4, wherein the cluster manager is configured to poll each of the plurality of LDAP servers.

6. The method of claim 1, wherein the proxy server is configured to process an LDAP search request, and choosing an LDAP server is based on criteria including proximity to an LDAP database and workload parameters.

7. An apparatus comprising:

a physical computing device comprising a main memory and a cluster manager in communication with the main memory;

an LDAP server cluster comprising a plurality of LDAP servers including a first LDAP server tightly coupled to a first database and a second LDAP server tightly coupled to a second database, wherein the cluster manager is configured to manage the plurality of LDAP servers in the LDAP server cluster, said cluster manager being configured to maintain status information for each of the plurality of LDAP servers;

a storage unit that stores a proximity list for the plurality of LDAP servers in ascending order of path length from the first database tightly coupled with said first LDAP server;

a proxy server configured to obtain said status information from the cluster manager, the status information indicating that the first LDAP server is not in a normal working state;

a connection between the proxy server and said cluster manager, said connection being configured for the proxy server to obtain said status information from the cluster manager;

a connection medium which interconnects each of the plurality of LDAP servers with all of a plurality of databases, each of which is respectively associated with one of the plurality of LDAP servers, and wherein the cluster manager is configured to access each of said plurality of databases; and

network means connecting the proxy server with a client;

wherein the cluster manager is configured to access the proxy server and employ the proxy server to process client requests for the plurality of LDAP servers;

wherein the proxy server is configured to choose the second LDAP server from the LDAP server cluster to execute a client request for data from the first database based on said status information received from the cluster manager indicating that the first LDAP server is not in the normal working state and the proximity list; and

wherein each LDAP server among the plurality of LDAP servers is at least loosely coupled with each of the plurality of databases, and is tightly coupled with a respective one of the plurality of databases; and

wherein the cluster manager is configured to choose an LDAP server via employing a suffix-to-database mapping table.

8. The apparatus of claim 7, wherein the cluster manager is coupled with the LDAP server cluster.

9. The apparatus of claim 8, wherein said each of the plurality of LDAP servers is in communication with all of the databases.

10. The apparatus of claim 7, wherein the cluster manager is arranged to perform at least one of configuring each of the plurality of LDAP servers with configuration information of the cluster manager, and configuring the cluster manager with configuration information of the plurality of LDAP servers, and configured to poll each of the plurality of LDAP servers at predetermined intervals for status updates;

and

wherein the second LDAP server is determined to be most proximate among the plurality of LDAP servers in the normal working state.

11. The apparatus of claim 7, wherein the cluster manager is configured to access the proxy server which is coupled to the client, the cluster manager being configured to receive the client request via the proxy server.

12. The apparatus of claim 11, wherein the cluster manager is configured to employ the proxy server to choose an LDAP server from the LDAP server cluster to perform the client request.

13. The apparatus of claim 12, wherein the cluster manager is configured to employ the proxy server via processing an LDAP search request and choose an LDAP server based on criteria including proximity to an LDAP database and workload parameters.

14. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform a method for managing a lightweight directory access protocol (LDAP) server in an LDAP server cluster, the method comprising:

providing a cluster manager in the LDAP server cluster comprising a plurality of LDAP servers including a first LDAP server tightly coupled to a first database and a second LDAP server tightly coupled to a second database, wherein the cluster manager is configured to manage the LDAP server cluster, said cluster manager being configured to maintain status information for each of the plurality of LDAP servers;

maintaining a proximity list for the plurality of LDAP servers in ascending order of path length from the first database tightly coupled with said first LDAP server;

providing a connection between a proxy server and said cluster manager, and configuring the proxy server to obtain said status information from the cluster manager;

providing databases respectively associated with each of the plurality of LDAP servers;

connecting each of the plurality of LDAP servers with all of said databases;

configuring the proxy server to process requests for the LDAP server cluster, wherein the proxy server is communicatively coupled with a client;

receiving, at the proxy server, a client request for data from the first database;

determining from said status information that the first LDAP server is not in a normal working state; and

selecting, by the proxy server, the second LDAP server from the LDAP server cluster to execute the client request based on said status information received from the cluster manager received from the cluster manager and said proximity list;

wherein each LDAP server among the plurality of LDAP servers is at least loosely coupled with each of the plurality of databases, and is tightly coupled with a respective one of the plurality of databases; and

wherein the second LDAP server is determined to be most proximate among the plurality of LDAP servers in the normal working state; and

wherein a suffix-to-database mapping table is employed to execute the client request.

15. A method of managing an LDAP server cluster comprising a cluster manager connected to each of a plurality of LDAP servers, the method comprising:

connecting each of the plurality of LDAP servers to all databases in a plurality of databases, wherein a first LDAP server among the plurality of LDAP servers is tightly coupled to a first database among the plurality of databases and a second LDAP server among the plurality of LDAP servers is tightly coupled to a second database among the plurality of databases;

maintaining a proximity list for the plurality of LDAP servers in ascending order of path length from the first database tightly coupled with said first LDAP server;

configuring the cluster manager to receive status information about each of the plurality of LDAP servers in the LDAP server cluster;

receiving at a proxy server a client request concerning data in the first database;

providing server status information for the first LDAP server and the second LDAP server from the cluster manager to the proxy server, wherein the server status information indicates that the first is not in a normal working state; and

selecting, by the proxy server, the second LDAP server from among the plurality of LDAP servers to execute the client request based on the server status information indicating that the first LDAP server is not in the normal working state and the proximity list. and

wherein a suffix-to-database mapping table is employed to execute the client request.

16. The method of claim 15, further comprising:

sending a server status request from the proxy server to the cluster manager in response to receiving the client request; and

responding to the status request by returning the server status information from the cluster manager to the proxy serverz

wherein the second LDAP server is determined to be most proximate among the plurality of LDAP servers in the normal working state.

17. The method of claim 15, wherein, if the client request is a database change request then the server status information includes status information for at least the first LDAP server.

18. The method of claim 15, wherein, if the client request is not a database change request then the server status information includes status information for each of the plurality of LDAP servers in the LDAP server cluster.

19. The method of claim 15, wherein said client request is a first client request and said proxy server is a first proxy server, the method further comprising:

receiving at a second proxy server a second client request concerning data in a second database;

sending a server status request from the second proxy server to the cluster manager in response to receiving the second client request; and

responding to the second status request by returning status information for a second LDAP server from the cluster manager to the second proxy server.