Global session identifiers in a multi-node system

• US 20060200469A1
• Filed: 03/02/2005
• Published: 09/07/2006
• Est. Priority Date: 03/02/2005
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Bastawala, Mehul, Gollapudi, Sreenivas, Kaluskar, Sanjay, Chidambaran, Lakshminarayanan
• Application Number:
  US11/071,275
• Publication Number:
  US 20060200469A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

A method and apparatus for managing sessions across the nodes of a multi-node system is provided. When a session is first initiated on any node of a multi-node system, a global session identifier is assigned to the session. The global session identifier uniquely identifies the session relative to all other sessions managed by the multi-node system. A session monitor may use the global session identifier to collect and store cumulative statistics about the activity of the session, regardless of which node of the multi-node system is currently managing the session, since the global session identifier uniquely identifies the session relative to all other sessions managed by the multi-node system. As a session may be uniquely identified across the lifetime of the session, the session state may be cleaned-up when the session ceases to be maintained, and the activity of the session during its lifetime may be analyzed.

Claims

1. A machine-implemented method, comprising:

initiating a session on a node of a multi-node system;

in response to initiating the session, assigning a global identifier to said session,

wherein said global identifier uniquely identifies said session relative to all other sessions managed by the multi-node system.

2. The method of claim 1, wherein the global identifier does not reflect the node, of the multi-node system, that is currently managing the session.

3. The method of claim 1, further comprising the step of:

migrating the session from a first node to a second node without changing the global identifier used to identify the session.

4. The method of claim 1, further comprising the step of:

in response to the node becoming inoperable, recreating the session on a second node of the multi-node system using, at least in part, the global identifier.

5. The method of claim 1, wherein said step of assigning the global identifier is performed by the node of the multi-node system.

6. The method of claim 1, wherein said step of assigning the global identifier is performed by a client of the multi-node system.

7. The method of claim 1, further comprising the step of:

transmitting, from a client of the multi-node system, to a particular node of the multi-node system, a request to initiate the session on the particular node, wherein the request identifies the global identifier.

8. The method of claim 1, further comprising the step of:

communicating the global identifier to a client, wherein the client requested that the session be initiated on the node.

9. The method of claim 1, wherein said session is a first session, wherein the first session is associated with a first user, and the method further comprises the step of:

in response to receiving, from a second user, at a particular node of the multi-node system, a request to initiate a second session on the particular node, wherein the request identifies the global identifier, performing the step of;

determining whether the first user is the same user as the second user.

10. The method of claim 9, further comprising the step of:

in response to determining that the first user is not the second user, denying the request to initiate the second session on the particular node.

11. The method of claim 1, wherein the global identifier is generated, at least in part, by using one or more of the following:

a database sequence, information identifying a node, a timestamp, and a random number.

12. The method of claim 1, wherein the global identifier comprises a portion that identifies one or more of the following:

a user that initiated the global identifier, a group associated with the user that initiated the global identifier, and a client that initiated the global identifier.

13. The method of claim 1, further comprising the step of:

storing data that establishes a limit on how long the session may be maintained by the multi-node system.

14. The method of claim 13, wherein the limit of how long the session may be maintained is measured by one or more of the following:

how much resources the session has consumed and a configurable amount of time.

15. The method of claim 13, further comprising the step of:

in response to determining that the limit has been exceeded, ceasing to maintain the session.

16. The method of claim 15, further comprising the step of:

in response to ceasing to maintain the session, ceasing to maintain any state information, for the session, using, at least in part, the global identifier.

17. The method of claim 1, further comprising the step of:

maintaining cumulative statistics about the session.

18. The method of claim 17, further comprising the step of:

determining how many nodes, of the multi-node system, managed the session during the lifetime of the session using, at least in part, the cumulative statistics.

19. The method of claim 17, further comprising the step of:

determining how much time elapsed during the lifetime of the session using, at least in part, the cumulative statistics.

20. The method of claim 17, further comprising the step of:

determining how many times the session migrated from a first node to a second node using, at least in part, the cumulative statistics.

21. The method of claim 17, further comprising the step of:

determining if the frequency that the session migrates between a set of nodes, of the multi-node system, exceeds a configurable threshold using, at least in part, the cumulative statistics.

22. The method of claim 17, further comprising the step of:

determining the location of any state information that is being maintained for the session using, at least in part, the cumulative statistics.

23. The method of claim 17, further comprising the step of:

determining a monetary value associated with the lifetime of the session using, at least in part, the cumulative statistics.

24. The method of claim 1, wherein the multi-node system is multi-node database system.

25. The method of claim 1, further comprising the step of:

in response to ceasing to maintain the session, performing the steps of;

identifying, using the global session identifier, one or more locations that are storing session state information for the session; and

ceasing to maintain, at the one or more locations, the session state information for the session.

26. A machine-implemented method, comprising:

while the session is being managed by a first node, of a multi-node system, generating first statistics about the session;

migrating the session from the first node to a second node of the multi-node system; and

after migrating the session from the first node to the second node, continuing the maintain the first statistics that were generated while the session was being managed by the first node, in association with the session, as the session is being managed on the second node.

27. A machine-readable medium carrying one or more sequences of instructions, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

initiating a session on a node of a multi-node system;

in response to initiating the session, assigning a global identifier to said session,

wherein said global identifier uniquely identifies said session relative to all other sessions managed by the multi-node system.

28. The machine-readable medium of claim 27, wherein the global identifier does not reflect the node, of the multi-node system, that is currently managing the session.

29. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

migrating the session from a first node to a second node without changing the global identifier used to identify the session.

30. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to the node becoming inoperable, recreating the session on a second node of the multi-node system using, at least in part, the global identifier.

31. The machine-readable medium of claim 27, wherein said step of assigning the global identifier is performed by the node of the multi-node system.

32. The machine-readable medium of claim 27, wherein said step of assigning the global identifier is performed by a client of the multi-node system.

33. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

transmitting, from a client of the multi-node system, to a particular node of the multi-node system, a request to initiate the session on the particular node, wherein the request identifies the global identifier.

34. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

communicating the global identifier to a client, wherein the client requested that the session be initiated on the node.

35. The machine-readable medium of claim 27, wherein said session is a first session, wherein the first session is associated with a first user, and wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to receiving, from a second user, at a particular node of the multi-node system, a request to initiate a second session on the particular node, wherein the request identifies the global identifier, performing the step of;

determining whether the first user is the same user as the second user.

36. The machine-readable medium of claim 35, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to determining that the first user is not the second user, denying the request to initiate the second session on the particular node.

37. The machine-readable medium of claim 27, wherein the global identifier is generated, at least in part, by using one or more of the following:

a database sequence, information identifying a node, a timestamp, and a random number.

38. The machine-readable medium of claim 27, wherein the global identifier comprises a portion that identifies one or more of the following:

a user that initiated the global identifier, a group associated with the user that initiated the global identifier, and a client that initiated the global identifier.

39. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

storing data that establishes a limit on how long the session may be maintained by the multi-node system.

40. The machine-readable medium of claim 39, wherein the limit of how long the session may be maintained is measured by one or more of the following:

how much resources the session has consumed and a configurable amount of time.

41. The machine-readable medium of claim 39, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to determining that the limit has been exceeded, ceasing to maintain the session.

42. The machine-readable medium of claim 39, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to ceasing to maintain the session, ceasing to maintain any state information, for the session, using, at least in part, the global identifier.

43. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

maintaining cumulative statistics about the session.

44. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining how many nodes, of the multi-node system, managed the session during the lifetime of the session using, at least in part, the cumulative statistics.

45. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining how much time elapsed during the lifetime of the session using, at least in part, the cumulative statistics.

46. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining how many times the session migrated from a first node to a second node using, at least in part, the cumulative statistics.

47. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining if the frequency that the session migrates between a set of nodes, of the multi-node system, exceeds a configurable threshold using, at least in part, the cumulative statistics.

48. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining the location of any state information that is being maintained for the session using, at least in part, the cumulative statistics.

49. The machine-readable medium of claim 43, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

determining a monetary value associated with the lifetime of the session using, at least in part, the cumulative statistics.

50. The machine-readable medium of claim 27, wherein the multi-node system is multi-node database system.

51. The machine-readable medium of claim 27, wherein execution of the one or more sequences of instructions by the one or more processors causes the one or more processors to further perform the step of:

in response to ceasing to maintain the session, performing the steps of;

identifying, using the global session identifier, one or more locations that are storing session state information for the session; and

ceasing to maintain, at the one or more locations, the session state information for the session.

52. A machine-readable medium carrying one or more sequences of instructions, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

while the session is being managed by a first node, of a multi-node system, generating first statistics about the session;

migrating the session from the first node to a second node of the multi-node system; and

after migrating the session from the first node to the second node, continuing the maintain the first statistics that were generated while the session was being managed by the first node, in association with the session, as the session is being managed on the second node.