System and method for multi-version remote function execution control in a distributed computing environment

• US 10,129,361 B2
• Filed: 07/01/2016
• Issued: 11/13/2018
• Est. Priority Date: 07/01/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Raja, Harvey, Gleyzer, Gene, Seovic, Aleksandar
• Primary Examiner(s): Bui, Jonathan A
• Application Number:
  US15/200,906
• Publication Number:
  US 20170006129A1
• Time in Patent Office: 865 Days
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A system and method for supporting multi-version remote function execution control in a distributed computing environment is provided. Remote functions are provided with a version identifier which uniquely identifies the version of the remote function. The version identifier can be a digest of the class definition of the remote function. The version identifier is used by an executor and/or class loader to ensure execution of correct class versions when on a node in a distributed computing environment. The definitive identification of class versions also provides for conditional transmission of class definition thereby reducing communication overhead for distribution of remote functions.

Claims

1. A method for supporting multi-version remote function execution control in a distributed computing environment, the method comprising:

receiving, at an executor from a first submitter, a first submitter classfile, the first submitter classfile including a version identifier, the version identifier being associated with a class definition for a remote function;

comparing by the executor the version identifier received from the first submitter against an original plurality of version identifiers;

responsive to the comparing finding no matches between the version identifier received from the first submitter and the original plurality of version identifiers, requesting by the executor, from the first submitter, the class definition of the remote function associated with the version identifier received from the first submitter;

receiving, at the executor from the first submitter responsive to the requesting, the class definition of the remote function associated with the version identifier received from the first submitter;

responsive to receiving the class definition of the remote function associated with the version identifier received from the first submitter, performing the remote function by the executor using the class definition for the remote function, and updating by the executor the original plurality of version identifiers as an updated plurality of version identifiers by adding to the original plurality of version identifiers the version identifier associated with the class definition for the remote function received from the first submitter;

receiving, at the executor from a second submitter after the updating of the original plurality of version identifiers to the updated plurality of version identifiers, a second submitter classfile, the second submitter classfile including the version identifier;

comparing by the executor the version identifier received from the second submitter against the updated plurality of version identifiers; and

responsive to the comparing finding a match between the version identifier received from the second submitter and the updated plurality of version identifiers, performing the remote function by the executor using the class definition previously received from the first submitter.

2. The method of claim 1, wherein the version identifier is a digest of the class definition of the remote function.

3. The method of claim 1, wherein the version identifier is an MD5 hash of the class definition of the remote function.

4. The method of claim 1, further comprising:

receiving the class definition of the remote function at the executor; and

using a classloader to load the remote function defined by the class definition for execution by said executor.

5. The method of claim 1, further comprising:

preparing said first submitter classfile by said first submitter; and

preparing said second submitter classfile by said second submitter.

6. The method of claim 1, further comprising:

preparing said first submitter classfile by said first submitter, wherein said preparing said first submitter classfile includes preparing said version identifier by performing a digest of said class definition; and

preparing said second submitter classfile by said second submitter, wherein said preparing said second submitter classfile includes preparing said version identifier by performing said digest of said class definition.

7. The method of claim 1, further comprising:

preparing said first submitter classfile by said first submitter, wherein preparing said first submitter classfile includes preparing said version identifier by performing an MD5 hash of said class definition; and

preparing said second submitter classfile by said second submitter, wherein preparing said second submitter classfile includes preparing said version identifier by performing said MD5 hash of said class definition.

8. The method of claim 1, further comprising:

the first submitter;

transmitting a first request calling for execution of the first submitter classfile by the executor without the first submitter submitting the class definition for the remote function.

9. The method of claim 1, further comprising:

the first submitter;

transmitting a first request calling for execution of the first submitter classfile by the executor; and

submitting the class definition for the remote function if the first submitter has made no prior request calling for the execution of the first submitter classfile by the executor.

10. The method of claim 1, wherein the requesting by the executor, from the first submitter, the class definition of the remote function associated with the version identifier received from the first submitter comprises:

transmitting by the executor a Request For Information (RFI) to the first submitter.

11. A system supporting multi-version remote function execution control in a distributed computing environment comprising:

a computer server comprising a microprocessor and memory;

a node operating on the computer server; and

an executor operating on the node, the executor configured to;

receive from a first submitter a first submitter classfile, the first submitter classfile including a version identifier, the version identifier being associated with a class definition for a remote function;

compare the version identifier received from the first submitter against an original plurality of version identifiers;

responsive to the comparing finding no matches between the version identifier received from the first submitter and the original plurality of version identifiers, request, from the first submitter, the class definition of the remote function associated with the version identifier received from the first submitter;

receive from the first submitter responsive to the request the class definition of the remote function associated with the version identifier received from the first submitter;

responsive to receiving the class definition of the remote function associated with the version identifier received from the first submitter, perform the remote function using the class definition for the remote function, and update the original plurality of version identifiers as an updated plurality of version identifiers by adding to the original plurality of version identifiers the version identifier associated with the class definition for the remote function received from the first submitter;

receive from a second submitter after the updating of the original plurality of version identifiers to the updated plurality of version identifiers, a second submitter classfile, the second submitter classfile including the version identifier;

compare the version identifier received from the second submitter against the updated plurality of version identifiers; and

responsive to the comparing finding a match between the version identifier received from the second submitter and the updated plurality of version identifiers, perform the remote function using the class definition previously received from the first submitter;

wherein the executor, the first submitter and the second submitter are processes.

12. The system of claim 11, wherein the version identifier is a digest of the class definition of the remote function.

13. The system of claim 11, wherein the version identifier is an MD5 hash of the class definition of the remote function.

14. The system of claim 11, wherein the executor is further configured to:

receive the class definition of the remote function; and

use a classloader to load the remote function defined by the class definition for execution by said executor.

15. The system of claim 11, further comprising:

the first and second submitters, wherein;

the first submitter is configured to prepare said first submitter classfile, wherein said preparing said first submitter classfile includes preparing said version identifier by performing a digest of said class definition; and

the second submitter is configured to prepare said second submitter classfile, wherein said preparing said second submitter classfile includes preparing said version identifier by performing the digest of said class definition.

16. The system of claim 11, further comprising:

the first and second submitters, wherein;

the first submitter is configured to prepare said first submitter classfile, wherein said preparing said first submitter classfile includes preparing said version identifier by performing an MD5 hash of said class definition; and

the second submitter is configured to prepare said second submitter classfile, wherein said preparing said second submitter classfile includes preparing said version identifier by performing said MD5 hash of said class definition.

17. The system of claim 11, further comprising:

the first submitter, wherein the first submitter is configured to transmit a request calling for execution of the first submitter classfile by the executor without submitting the class definition for the remote function.

18. The system of claim 11, further comprising:

the first submitter, wherein the first submitter is configured to;

request calling for execution of the first submitter classfile by the executor; and

submit the class definition for the remote function if the first submitter has made no prior request calling for the execution of the first submitter classfile by the executor on said node.

19. The system of claim 11, wherein the executor is further configured to:

request the class definition of the remote function by transmitting a Request For Information (RFI) to the first submitter.

20. A non-transitory computer-readable medium having instruction stored thereon for supporting multi-version remote function execution control in a distributed computing environment, which instructions, when executed cause a computer system in the distributed computing environment to perform steps comprising:

receiving, at an executor from a first submitter, a first submitter classfile, the first submitter classfile including a version identifier, the version identifier being associated with a class definition for a remote function;

comparing by the executor the version identifier received from the fist submitter against an original plurality of version identifiers;

responsive to the comparing finding no matches between the version identifier received from the first submitter and the original plurality of version identifiers, requesting by the executor, from the first submitter, the class definition of the remote function associated with the version identifier received from the first submitter;

receiving, at the executor from the first submitter responsive to the requesting, the class definition of the remote function associated with the version identifier received from the first submitter;

responsive to receiving the class definition of the remote function associated with the version identifier received from the first submitter, performing the remote function by the executor using the class definition for the remote function, and updating by the executor the original plurality of version identifiers as an updated plurality of version identifiers by adding to the original plurality of version identifiers the version identifier associated with the class definition for the remote function received from the first submitter;

receiving, at the executor from a second submitter after the updating of the original plurality of version identifiers to the updated plurality of version identifiers, a second submitter classfile, the second submitter classfile including the version identifier;

comparing by the executor the version identifier received from the second submitter against the updated plurality of version identifiers; and

responsive to the comparing finding a match between the version identifier received from the second submitter and the updated plurality of version identifiers, performing the remote function by the executor using the class definition previously received from the first submitter;

wherein the executor, the first submitter and the second submitter are processes.