Naming service in a clustered environment

• US 20050278339A1
• Filed: 05/27/2004
• Published: 12/15/2005
• Est. Priority Date: 05/27/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Petev, Petio, Pancheva, Elitsa
• Granted Patent: US 9,122,686 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

Within a cluster, when a new server node joins the cluster, an indication of the new server node has joined is received by at least one server node in the cluster. Global naming operations are disabled within the cluster. While the global naming operations are disabled, the global naming objects are replicated to the new server node. Once the replication is complete, global naming is reenabled for the cluster. In one embodiment of the invention, subsequent naming data from subsequent global naming operations is replicated in all server nodes in the cluster. One embodiment of the invention redirects naming operations directed to a down server node to a different server node within the cluster. One embodiment of the invention performs security checks responsive to a first access to the naming service.

Claims

1. A system comprising:

a first server node;

a second server node;

a first naming service and a second naming service executing in the first server node and the second server node respectively, wherein each naming service includes a replication engine to replicate global naming data to the other of the first server node and the second server node.

2. The system of claim 1 further comprising:

a security service to provide security interface for at least one of the first naming service and the second naming service.

3. The system of claim 2 wherein the security service provides authorization only when an initial context is requested by a remote client.

4. The system of claim 1 wherein each naming service further comprises:

an identifier generator (IDG) to generate global unique identifiers (GUIDS) for the global naming data.

5. The system of claim 4 wherein the IDG comprises:

a counter to count global objects and contexts bound and created respectively in the system.

6. The system of claim 1 further comprising:

a connection service to provide a connection between a remote client and at least one of the first server node and the second server node.

7. The system of claim 6 wherein the connection service provides remote method invocation (RMI).

8. The system of claim 6 further comprising:

a cross service to redirect the connection from a first server node to a second server node if the first server node fails.

9. The system of claim 1 further comprising:

a locking service to prevent global naming operations in the system while a new server node joins the system; and

a replication engine in the new server node to replicate all global naming data in the new server node.

10. A method comprising:

receiving an indication that a new server node is joining a cluster of server nodes;

disabling global naming operations within the cluster;

replicating global naming objects in the new server node; and

enabling global naming operations once replicating is complete.

11. The method of claim 10 further comprising:

identifying in a server node a global naming operation;

notifying other server nodes in the cluster of the global naming operation.

12. The method of claim 11 further comprising:

generating a unique global identifier for global objects from a server identifier of a creating server and a consecutive number of the global naming objects and contexts.

13. The method of claim 10 further comprising:

redirecting a naming operation from a remote client directed to a target server node to a second server node if the target server node is down.

14. The method of claim 13 wherein redirecting comprises:

obtaining a name with which the second server is registered with a cross service; and

connecting a stub from the remote client to a skeleton from the second server.

15. The method of claim 10 further comprising:

checking an authorization of a remote client to use naming operations within the cluster only a first time the remote client attempts to access a naming service.

16. The method of claim 10 further comprising:

authenticating a remote client responsive to a request for an initial context.

17. An apparatus comprising:

means for replicating global naming operations to a server node joining a cluster; and

means for notifying the cluster of global naming operations in any server node.

18. The apparatus of claim 17 further comprising:

means for redirecting naming operation to a second server node in the event of target server node failure.

19. The apparatus of claim 17 further comprising:

means for generating a global unique identifier for each global object.

20. The apparatus of claim 17 further comprising:

means for authenticating a client attempting naming operations; and

means for performing one time authorization of a client a first time a naming operation is attempted by the client. (get InitialContext operation)

21. A machine accessible medium containing instructions that, when executed, cause a machine to:

receive an indication that a new server node is joining a cluster of servers;

disable global naming operations within the cluster;

replicate global naming objects in the new server; and

enable global naming operations once replicating is complete.

22. The machine accessible median of claim 21 wherein the instructions further comprise instructions to cause the machine to:

identify in a server node a global naming operation;

notify other server nodes in the cluster of the global naming operation.

23. The machine accessible median of claim 22 wherein the instructions further comprise instructions to cause the machine to:

generate a unique global identifier for global objects from a server identifier of a creating server and a consecutive number of the global naming operation.

24. The machine accessible median of claim 21 wherein the instructions further comprise instructions to cause the machine to:

redirect a naming operation from a remote client directed to a target server node to a second server node if the target server node is down.

25. The machine accessible median of claim 24 wherein instructions causing the machine to redirect comprise instructions to cause the machine to:

obtain a name with which the second server is registered with a cross service; and

connect a stub from the remote client to a skeleton from the second server.

26. The machine accessible median of claim 21 wherein the instructions further comprise instructions to cause the machine to:

check an authorization of a remote client to use naming operations within the cluster only a first time the remote client attempts to access the naming operations.

27. The machine accessible median of claim 21 wherein the instructions further comprise instructions to cause the machine to:

authenticate a remote client responsive to a request for an initial context.