Execution path determination in a distributed environment

Patent metadata

Field	Value
Publication number	US-11360785-B2
Application number	US-201916597764-A
Country	US
Kind code	B2
Filing date	Oct 9, 2019
Priority date	Sep 28, 2012
Publication date	Jun 14, 2022
Grant date	Jun 14, 2022

Abstract

Techniques to determine an execution path in a distributed environment are disclosed. A call to a method or function of a component of the distributed system is received, in connection with a request from a user of the distributed system. A unique correlation identifier that includes data that identifies the component, the request, and the method of function called is generated for the call.

First claim

What is claimed is:

1. A method of processing a request in a distributed system, comprising:
receiving, by one or more processors associated with a first component of the distributed system, in connection with a request from a client device of the distributed system, a first call to a method or function of the first component;
generating a unique request identifier corresponding to the request;
storing the unique request identifier in a manner that associates the unique request identifier with a related runtime context by storing a session or other state information related to the client device with the unique request identifier, wherein the request identifier includes a counter with a value corresponding to a number of requests received by the first component, wherein the unique correlation identifier further comprises data that identifies: a request counter identifier that identifies the request in relation to another request received by the distributed system;
generating, by the one or more processors associated with the first component of the distributed system, a unique correlation identifier for the first call, the unique correlation identifier comprising data that identifies: the first component associated with the request, a method counter identifier indicating a sequential place of the first call within a sequence of calls associated with the request; and
providing, by the one or more processors associated with the first component of the distributed system, the unique correlation identifier to a second component,
wherein the first component corresponds to one of a plurality of components of the distributed system.

2. The method of claim 1 , wherein the distributed system comprises a plurality of products integrated to provide the distributed system and the first component includes one or more of the products.

3. The method of claim 1 , wherein the unique correlation identifier further comprises data that identifies: an identifier of a method of the first component or a function of the first component that is called.

4. The method of claim 1 , wherein the unique correlation identifier is provided to the second component of the distributed system in connection with a second call by the first component to the second component in connection with the request from the client device.

5. The method of claim 1 , further comprising storing the unique correlation identifier.

6. The method of claim 1 , further comprising providing the unique correlation identifier as output.

7. The method of claim 1 , further comprising using the unique correlation identifier to analyze a failure associated with the request.

8. The method of claim 1 , further comprising using the unique correlation identifier to analyze a system performance issue associated with the request.

9. The method of claim 1 , further comprising parsing the unique correlation identifier to determine at least in part programmatically an execution path or portion thereof associated with the request.

10. The method of claim 1 , wherein a second call is received from another component of the distributed system.

11. The method of claim 10 , wherein receiving the second call includes receiving in connection with the second call a latest correlation identifier of the component from which the second call is received.

12. The method of claim 11 , further comprising using the latest correlation identifier of the component from which the second call is received to generate the unique correlation identifier for the second call.

13. The method of claim 12 , wherein receiving the first call includes receiving in connection with the first call a calling party correlation identifier associated with the first call into the calling method or function.

14. The method of claim 11 , further comprising including at least a portion of the latest correlation identifier of the component from which the second call is received in the unique correlation identifier for the second call.

15. The method of claim 1 , wherein the first call is received from a calling method or function of the first component but external to a called library with which the called method or function is associated.

16. The method of claim 1 , wherein the request counter identifier corresponds to an integer n, which indicates that the request received at the first component corresponds to an nth request received by the first component.

17. The method of claim 1 , wherein the unique identifier for the first call to the method or function of the first component is serialized with additional information to form an inter-product correlation identifier, such additional information identifying: the second component to which the second call is made by the first component, a method of the second component subject to the second call made by the first component, and a method counter identifier that identifies the method associated with the second component that is called in connection with the request in relation to other methods of the second component called in connection with the request.

18. The method of claim 1 , wherein the unique correlation identifier is associated with a runtime context with which the request is associated.

19. The method of claim 1 , further comprising:
receiving, at the second component, the unique correlation identifier in connection with a second call from the first component;
determining a local correlation identifier in connection with a third call to be made by the second component to a third component of the plurality of components in the distributed system; and
generating a combined correlation identifier, wherein the combined correlation identifier includes the local correlation identifier and at least a part of the unique correlation identifier.

20. The method of claim 19 , wherein the generating the combined correlation identifier comprises serializing the local correlation identifier with the unique correlation identifier.

21. A distributed system, comprising:
a processor configured to:
receive at a first component of the distributed system, in connection with a request from a client device of the distributed system, a first call to a method or function of the first component;
generate a unique request identifier corresponding to the request;
store the unique request identifier in a manner that associates the unique request identifier with a related runtime context by storing a session or other state information related to the client device with the unique request identifier, wherein the request identifier includes a counter with a value corresponding to a number of requests received by the first component, wherein the unique correlation identifier further comprises data that identifies: a request counter identifier that identifies the request in relation to another request received by the distributed system;
generate for the first call a unique correlation identifier that includes data that identifies the first component associated with the request, a method counter identifier indicating a sequential place of the first call within a sequence of calls associated with the request; and
provide the unique correlation identifier to a second component; and

a memory or other storage device coupled to the processor and configured to store the unique correlation identifier;
wherein the first component corresponds to one of a plurality of components of the distributed system.

22. A computer program product embodied in a tangible, non-transitory

Assignees

• Emc Ip Holding Co Llc

Inventors

• Kumar Vinod

Classifications

• G06F9/50

  Allocation of resources, e.g. of the central processing unit [CPU] · CPC title

• G06F9/5038 Primary

  considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups) · CPC title

• G06F11/3466

  Performance evaluation by tracing or monitoring · CPC title

• G06F9/445 Primary

  Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57) · CPC title

• G06F9/455

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title