Dynamic server directory for distributed computing system

• US 20020152293A1
• Filed: 01/31/2001
• Published: 10/17/2002
• Est. Priority Date: 01/31/2001
• Status: Abandoned Application

• Current Assignee: Agami Systems, Inc.
• Original Assignee: Agami Systems, Inc.
• Inventors: Earl, William, Qureshi, Waheed, Feinberg, George, Nowicki, Kacper, Ramos, Luis, Hahn, Terry G.
• Application Number:
  US09/773,059
• Publication Number:
  US 20020152293A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

According to one embodiment, a dynamic server directory (DSD) (300) may include a number of relational tables (302 to 314) having a number of entries. Entries of selected tables (304 to 306) may include information for a server in a distributed computing system. Such information may include a server identification, host machine identification, and server status information. Entries of another table (308) may include host route information. According to one embodiment, dynamic server directory agents (DSDAs), residing on the same machine as a client process, may cache tables of a DSD (300). For a given client request, a client may query a local DSDA to determine which server(s) may service the client request. The local DSDA may then return the route to one or more servers that are available to service the request. Server information in a DSD (300) may be changed in response to changes in server status. Such changes may then be forwarded to DSDAs. Clients may subscribe with the DSDA to receive notification of changes in server and route status. The client may then act in accordance with the change in status.

Claims

1. A dynamic server directory system, comprising:

at least one relational table that includes a plurality of entries that can each store location data, status data, and feature data of server processes in a distributed computing system that services client requests; and

an interface that may provide at least one entry from the at least one relational table to a client.

2. The dynamic server directory system of claim 1, wherein:

the location data of an entry may comprise a network address; and

the entry may include a server name to identify a specific server at the network address.

3. The dynamic server directory system of claim 1, further including:

a route table that can indicate at least one communication route to a server host and the status of said route.

4. The dynamic server directory system of claim 1, further including:

a plurality of dynamic server directory agents that reside on different host machines than the dynamic server directory, each dynamic server directory agent caching at least a portion of the at least one relational table.

5. The dynamic server directory system of claim 1, wherein:

the relational table includes a key field that may be searched by a key prefix value that can filter entries according to client request criteria

6. The dynamic server directory system of claim 1, further including:

a plurality of dynamic server directory agents that reside on different host machines than the dynamic server directory, each dynamic server directory agent forwarding new server process information to the dynamic server directory when a new server process is added; and

the dynamic server directory creating a new entry in the at least one relational table corresponding to the server process and forwarding the updated relational table to dynamic server directory agents.

7. The dynamic server directory system of claim 1, wherein:

the distributed computing system includes at least two subsystems that provide different functions; and

the at least one relational table includes a plurality of relational tables, each relational table including entries corresponding to server processes of one of the subsystems.

8. The dynamic server directory system of claim 1, wherein:

the at least one relational table includes a server relational table that identifies a server route corresponding to a given server process and a route relational table that identifies a communication route corresponding to a given host machine.

9. The dynamic server directory system of claim 8, further including:

the interface searches the server relational table and then the route relational table to determine the route to a host machine for a given server process.

10. The dynamic server directory system of claim 1, further including:

a plurality of dynamic server directory agents that reside on different host machines than the dynamic server directory, each dynamic server directory agent receiving periodic status communications from at least one server process and notifying the dynamic server directory when status communications fail; and

the dynamic server directory changes entries in the at least one relational table in response to status communication failures.

11. The dynamic server directory of claim 10, further including:

a service master process that may subscribe with the DSD agent to be notified of changes to the at least one relational table, the service master performing at least one predetermined error response when the change to the at least one relational table indicates a status communication failure has occurred in a server process; and

the dynamic server directory forwards changes in the at least one relational table to the DSD agent.

12. The dynamic server directory of claim 11, wherein:

the predetermined error response may be at least one response selected from the group consisting of;

attempting to restart the server process corresponding to the failure, logging the failure error, notifying a system administrator, generating a work order for the server process corresponding to the error, activating another server process as a back-up to the server process corresponding to the failure, shutting down a host machine for the server process corresponding to the failure, and rebooting a host machine for the server process corresponding to the failure.

13. The dynamic server directory of claim 1, wherein:

a plurality of client processes that may subscribe to be notified of changes to the at least one relational table, a client process performing a resubmission of all requests sent on a particular currently valid server route when the change to the at least one relational table indicates a failure in the server process, or the route to the server process.

15. The system of claim 14, wherein:

the plurality of servers include storage servers that may access stored files and metadata servers that may access metadata for the stored files.

16. The system of claim 14, wherein:

the dynamic server directory agent includes an inter face that may provide access to the relational tables in response to an action selected from the group consisting of;

the addition of a new entry to a relational table, deletion of a entry from a relational table, search for a key, search for a server, subscription to notification of changes in status, and maintenance of current process information.

17. The system of claim 14, further including:

the plurality of servers reside on server host machines; and

each server host machine further includes a dynamic server directory agent that caches at least a portion of at least one relational table and is accessible by a client.

19. The method of claim 18, wherein:

selecting a server includes a client invoking an interface function of a DSDA residing on the same host machine as the client.

20. The method of claim 18, wherein:

selecting a server includes searching a first server information relational table to determine a server route including a host machine on which a desired server resides, and searching a second server information relational table to determine a route to the host machine.

21. The method of claim 18, wherein:

the server information includes

at least one server relational table having entries that comprise server identification, server route identification including host machine identification, and a server status indication for each server process, and

at least one route relational table having entries that comprise host machine identification, route information, and host machine status indication.

22. The method of claim 21, further including:

the plurality of servers includes a gateway servers that control access to the distributed computing system, metadata servers that access metadata for stored files, and storage servers that store files; and

the at least one server relational table includes a gateway server relational table, a metadata server relational table, and a storage server relational table.

14. A system, comprising:

a plurality of servers that may perform predetermined operations according to requests from clients; and

a dynamic server directory that includes a plurality of relational tables, each relational table storing feature information for the plurality of servers, the feature information being accessible by a client to determine which server may service a particular client request; and

a plurality of dynamic server directory agents that may perform predetermined operations according to client subscriptions.

18. A method of controlling client requests in a distributed computing system having a plurality of servers, comprising the steps of:

maintaining server information in a dynamic server directory (DSD) for the servers that indicates availability of a server for particular client requests;

caching server information in dynamic server directory agents (DSDAs);

selecting a server for a particular client request from server information cached in a DSD;

monitoring servers with DSDAs and forwarding server status information to the DSD;

changing server information in the DSD for a selected server in response to server status information; and

forwarding changed server information to DSDAs.