# Patent

## Title
Dynamic scaling of a cluster of computing nodes used for distributed execution of a program

## Abstract

Techniques are described for managing distributed execution of programs, including by dynamically scaling a cluster of multiple computing nodes used to perform ongoing distributed execution of a program, such as to increase and/or decrease the quantity of computing nodes in the cluster at various times and for various reasons. An architecture may be used that facilitates the dynamic scaling of a cluster, including by having at least some of the computing nodes act as core nodes that each participate in a distributed storage system for the distributed program execution, and having one or more other computing nodes that act as auxiliary nodes that do not participate in the distributed storage system. If computing nodes are selected to be removed from the cluster during ongoing distributed execution of a program, one or more nodes of the auxiliary computing node type may be selected for the removal.

## Background
BACKGROUND
Many companies and other organizations operate computer networks that interconnect numerous computing systems to support their operations, such as with the computing systems being co-located (e.g., as part of a local network) or instead located in multiple distinct geographical locations (e.g., connected via one or more private or shared intermediate networks). Such groups of interconnected computing systems are increasingly useful for various reasons, including to support increasingly large software programs and input data sets that may be distributed across multiple computing systems.
Various approaches have been taken to providing groups of interconnected computing systems. For example, data centers housing significant numbers of interconnected co-located computing systems have become commonplace, such as private data centers that are operated by and on behalf of a single organization, and public data centers that are operated by entities as businesses to provide computing resources to customers. Some public data center operators provide network access, power, and secure installation facilities for hardware owned by various customers, while other public data center operators provide “full service” facilities that also include hardware resources made available for use by their customers. However, as the scale and scope of typical data centers and computer networks has increased, the task of provisioning, administering, and managing the associated physical computing resources has become increasingly complicated.
The advent of virtualization technologies for commodity hardware has provided some benefits with respect to managing large-scale computing resources for many customers with diverse needs, allowing various computing resources to be efficiently and securely shared by multiple customers. For example, virtualization technologies such as those provided by VMWare, XEN, Linux's KVM (“Kernel-based Virtual Machine”), or User-Mode Linux may allow a single physical computing machine to be shared among multiple users by providing each user with one or more virtual machines hosted by the single physical computing machine, with each such virtual machine being a software simulation acting as a distinct logical computing system that provides users with the illusion that they are the sole operators and administrators of a given hardware computing resource, while also providing application isolation and security among the various virtual machines.



BRIEF DESCRIPTION OF THE DRAWINGS
FIGS. 1A and 1B are network diagrams illustrating example embodiments of use of a distributed program execution service by remote users.
FIGS. 2A-2D illustrate examples of managing the monitoring and modifying of distributed program execution on multiple computing nodes.
FIG. 3 is a block diagram illustrating an example embodiment of a computing system for managing distributed program execution.
FIGS. 4A-4C illustrate a flow diagram of an example embodiment of a Distributed Program Execution Service System Manager routine.
FIG. 5 illustrates a flow diagram of an example embodiment of a routine for obtaining user-specified program execution configuration information.
FIG. 6 illustrates a flow diagram of an example embodiment of a routine for performing distributed program execution.
FIG. 7 illustrates a flow diagram of an example embodiment of a Computing Node Manager routine.



DETAILED DESCRIPTION
Techniques are described for managing distributed execution of programs. In at least some embodiments, the techniques include dynamically scaling a cluster of multiple computing nodes that are used to perform the ongoing distributed execution of a particular program, such as to increase and/or decrease the quantity of computing nodes in the cluster at various times and for various reasons during ongoing use of the cluster. In addition, in at least some embodiments, the managing of the distributed execution of a program on a cluster of multiple nodes includes using an architecture for the multiple computing nodes of the cluster that facilitates the dynamic scaling, including by having at least some of the computing nodes act as core nodes that each participate in a distributed storage system for the distributed program execution, and optionally having one or more other computing nodes that act as auxiliary nodes that do not participate in the distributed storage system. To perform the distributed execution of the program on the cluster, the program may be separated into multiple execution jobs that are each executed on one of the computing nodes of the cluster, such as by executing one or more of the execution jobs on each auxiliary node of the cluster and optionally on some or all of the core nodes of the cluster, and the architecture for the distributed program execution may further include one or more of the cluster computing nodes that act as administrative computing nodes to control or monitor at least some aspects of the distributed execution of the program on the other core and auxiliary computing nodes of the cluster. Additional details related to managing the distributed execution of programs are included below.
In at least some embodiments, some or all of the techniques may be automatically performed by a Distributed Program Execution (“DPE”) service, as described in greater detail below, such as a service that is provided by a corresponding automated system and that executes multiple programs on behalf of multiple customers or other clients of the service. Moreover, in addition to managing distributed execution of programs, such a DPE service may in some embodiments provide various computing nodes having access to various computing resources (e.g., local memory, local storage, local CPU cycles, networks between computing nodes and to external computing systems, remote storage, etc.) that are available for use in executing programs for clients in a distributed manner. The computing nodes used as part of a cluster for the distributed execution of a program may have various forms in various embodiments (e.g., may each be a physical computing system and/or a virtual machine that is hosted on one or more physical computing systems), and may each have access to various computing resources. As described in greater detail below, the computing resources used to execute a particular program may include particular quantities of multiple types of computing resources (e.g., an aggregate amount of RAM or other memory of one or more physical computing systems that is used, such as by one or more computing nodes; an aggregate amount of network bandwidth capacity used on one or more networks, such as by one or more computing nodes; an aggregate amount of storage space used on one or more storage devices, such as by one or more computing nodes, and optionally by using local storage devices of multiple computing nodes; etc.). Furthermore, the computing nodes that the DPE service uses may in some embodiments be of multiple resource configuration types that may be selected and used in different situations, with each resource configuration type having a distinct combination of associated computing resources for computing nodes of that type, as discussed in greater detail below.
As previously noted, a cluster for use in the distributed execution of a program may in at least some embodiments include multiple core computing nodes that participate in a distributed storage system for use by the cluster, such as to store input data used in the distributed program execution and/or output data generated by the distributed program execution. The distributed storage system may have various forms in various embodiments, such as a distributed file system, a distributed database, etc., and in some embodiments may provide various mechanisms to enhance data availability (e.g., by storing multiple copies of at least some groups of data, such as to enhance the likelihood that at least one copy of a particular group of data remains available if a core computing node storing another copy of that data group fails or otherwise becomes unavailable). When executing a particular execution job for a program on a computing node of a cluster for that program, information related to the execution may be accessed and used in various manners. For example, when the execution of the execution job is initiated on a computing node, the input data to be used by the execution job may be locally stored on the computing node (e.g., on a local hard disk or other local storage device) to facilitate access to that input data during execution, and any software instructions to be executed for the execution job may similarly be locally stored on the computing node. If the computing node on which the execution occurs is a core computing node that already locally stores the input data to be used as part of its participation in the distributed storage system (e.g., if that core computing node is selected to execute the execution job because it already locally stores that input data on a storage device of the core node), the execution may merely include retrieving and using that input data from the distributed storage system as needed, and storing any generated results in the local portion of the distributed storage system. Alternatively, if the computing node on which the execution occurs is a core node that does not already locally store the input data to be used or is an auxiliary computing node not participating in the distributed storage system, the computing node may retrieve that input data from one or more of the core nodes that do store that input data, locally store that retrieved data temporarily on the computing node, and optionally later send any generated results data to one or more core nodes for storage in the distributed storage system. Furthermore, in at least some embodiments, the input data and/or generated output data in the distributed storage system may further be exchanged with or otherwise stored in one or more remote storage locations, and in some embodiments such remote storage may be used in lieu of a local distributed storage system, as discussed in greater detail below.
The use of an architecture having core computing nodes and auxiliary computing nodes in a cluster may facilitate the dynamic scaling of the computing nodes for that cluster in various manners in various embodiments. For example, if a particular computing node will remain in a cluster until the use of the cluster ends (e.g., until the distributed execution of one or more programs by the cluster is completed), it is preferable in at least some embodiments to use that computing node as a core computing node participating in a distributed storage system for the cluster, as doing so increases the aggregate size of the distributed storage system, and may also allow that core computing node to more efficiently perform the execution of execution jobs for which it already locally stores associated input data. Alternatively, if a particular computing node will be removed from a cluster before the use of the cluster ends, it is preferable in at least some embodiments to use that computing node as an auxiliary computing node not participating in the distributed storage system for the cluster, as removing a local portion of the distributed storage system that would have been stored on that auxiliary node if it had instead been a core node while the cluster is in use may cause one or more of the copies of data stored in that local portion to be lost (e.g., if other copies of the data are not available), may cause additional work in recreating other copies (if possible) of the data stored in the local portion, and/or in some situations may cause some or all of the aggregate functionality of the entire distributed storage system to be lost (e.g., if the structure of the distributed storage system does not support the removal of a constituent computing node while the distributed storage system is in use).
Accordingly, core computing nodes and auxiliary computing nodes may be used in various manners in various clusters. When a cluster is created, some or all of the computing nodes in the cluster may initially be selected to be core computing nodes, and optionally zero or more of the computing nodes in the cluster may initially be selected to be auxiliary computing nodes. Similarly, when a cluster is dynamically modified while it is in use, a particular one of core computing nodes and auxiliary computing nodes may be selected as a type of computing node to be modified, such as to increase the quantity of computing nodes in the cluster by adding one or computing nodes of the selected type and/or to reduce the quantity of computing nodes in the cluster by removing one or more computing nodes of the selected type. If the quantity of computing nodes in a cluster is dynamically reduced while the cluster is in use, auxiliary computing nodes may be the only computing nodes that are selected for removal in some embodiments, while in other embodiments auxiliary computing nodes may preferably be selected for removal if they are available but with core computing nodes being removed if sufficient auxiliary computing nodes are not available in the cluster. If the quantity of computing nodes in a cluster is dynamically increased while the cluster is in use, one or both of the core and auxiliary computing node types may be selected for addition in at least some embodiments, such as based at least in part on the situation surrounding the increase (e.g., if the increase in the quantity is intended to be permanent until use of the cluster ends, then add core nodes, and otherwise add some or all of the additional computing nodes as auxiliary nodes if the increase may be temporary). In some embodiments and situations, a particular cluster may include only core computing nodes or only auxiliary computing nodes.
Situations in which a cluster of computing nodes may be dynamically modified while in use include the following non-exclusive examples. As a first example, the distributed execution of a program may use at least a minimum quantity of computing nodes at all times, and may occasionally use additional computing nodes (e.g., to temporarily increase the total quantity to handle temporary increases in computing load)—if so, the cluster may be created at a first time with a quantity of core computing nodes that corresponds to the minimum quantity, and with any other computing nodes that are temporarily added or subsequently removed at a later second time being auxiliary computing nodes. In such a situation, if the minimum quantity of computing nodes for the cluster is increased at a later second time while the cluster is in use, the new nodes added to reach the new higher minimum quantity may be selected to be additional core computing nodes. As a second example, the distributed execution of a program may have multiple distinct stages or phases, and different amounts of computing resources may be desired for the different stages or phases—if so, and if a later stage/phase is desired to have a lower quantity of computing nodes than an earlier stage/phase, the cluster may be initially created at a first time with a quantity of core computing nodes that corresponds to the lowest total quantity of cluster nodes that are expected for any of the stages/phases, and with any other computing nodes that are initially included at the first time or later added or removed at a second time being auxiliary computing nodes. As a third example, the distributed execution of a program may begin at a first time with a minimum quantity of computing nodes to achieve a desired goal (e.g., to be expected to complete the distributed program execution before a specified time), but may dynamically decide at a later second time to increase the quantity of computing nodes in the cluster during ongoing program execution based on current conditions at the second time (e.g., based on a cost of the additional computing nodes at the second time being sufficiently low; based on the status of the distributed program execution at the second time, such as having not reached a desired degree of completion; based on a particular specified second time being reached while the distributed program execution is ongoing; etc.)—if so, the cluster may be created with a quantity of core computing nodes that corresponds to the minimum quantity, and with any other computing nodes that are added at the later second time being selected to be core or auxiliary computing nodes depending on the planned permanence or temporariness, respectively, of the added nodes. It will be appreciated that a cluster may be dynamically modified while in use in various other situations and in various other manners.
As previously noted, the computing nodes that are available to be used in a cluster may in some embodiments and situations include multiple types of computing nodes having distinct computing resource configurations. If so, the different computing resource configuration computing node types may optionally be used as part of the dynamic scaling of the cluster in various manners in various embodiments. For example, in some such embodiments, all of the core computing nodes may be of a single resource configuration computing node type and all of the auxiliary computing nodes may be of a single resource configuration computing node type, but with the resource configuration computing node types being different for the core and auxiliary nodes—such a configuration may be useful if the different uses for the nodes involve different computing resource configurations (e.g., if the resource configuration computing node type for the core computing nodes includes at least a minimum amount of local storage for use within the distributed storage system, while the resource configuration computing node type for the auxiliary computing nodes includes at least a minimum amount of local memory and/or CPU cycles to facilitate the execution of execution jobs by the auxiliary nodes). In other embodiments, one or both of the core and auxiliary computing nodes may include computing nodes of multiple different resource configuration computing node types. In addition, the resource configuration computing node types may be further used as part of dynamic scaling of a cluster while the cluster is in use, such as to specify to add or to remove computing nodes of a specified resource configuration computing node type from the core and/or auxiliary computing nodes in the cluster (e.g., to add or remove a specified quantity of computing nodes of the specified resource configuration computing node type, to remove all computing nodes of the specified resource configuration computing node type from at least one of the core and auxiliary computing nodes, etc.). Computing nodes of different resource configuration computing node types may also have other differing attributes that are used to affect their selection and use in at least some embodiments, including an associated cost of use, as discussed in greater detail elsewhere.
The determination of whether and how to perform dynamic scaling for a cluster, including to add and/or remove core or auxiliary computing nodes that are optionally of a particular resource configuration computing node type, may be made in various manners in various embodiments. For example, in some embodiments, a user who is a client of the DPE service may interactively specify various information for use in the distributed execution of an indicated program, such as via a GUI (graphical user interface) of the DPE service. Such user-specified information may include instructions to perform one or more of the following non-exclusive list: to start a cluster at the current time (or at a different specified future time) with an indicated quantity of computing nodes (optionally with an indication of how many, if any, of the computing nodes are to be auxiliary computing nodes, although in some embodiments the use of auxiliary computing nodes may not be indicated to some or all clients); to dynamically modify a cluster at the current time (or at a different specified future time) by adding and/or removing an indicated quantity of computing nodes (optionally with an indication of whether the computing nodes are to be auxiliary computing nodes and/or core computing nodes, although in some embodiments the use of auxiliary computing nodes may not be indicated to some or all clients); and to perform other operations for a cluster (e.g., to suspend some or all of the execution, to resume previously suspended execution, etc.). In addition, in some embodiments, one or more scaling-related criteria may be defined for a cluster, whether by an associated client or by the DPE service, that specify particular actions to be performed if specified conditions are satisfied, including to dynamically modify a cluster by adding and/or removing an indicated quantity of computing nodes (optionally with an indication of whether the computing nodes are to be auxiliary computing nodes and/or core computing nodes); to use one or more computing nodes of a specified resource configuration type in a specified manner, including to add and/or remove computing nodes of that type for a particular cluster; etc. If a user instruction or defined scaling criteria specifies to add or remove one or more computing nodes without indicating whether the modification applies to core and/or auxiliary computing nodes, the DPE service may in at least some embodiments automatically select which type of computing nodes to use for the modification, such as by using rules or factors described in greater detail elsewhere. As is also discussed in greater detail elsewhere, the user-specified instructions and/or defined scaling criteria may in some embodiments further specify particular resource configuration computing node types to be used in various manners when adding or removing computing nodes. The defined scaling criteria may have various forms in various manners, including in some embodiments to be provided or analyzed by the DPE service by executing software instructions (e.g., as part of a program, applet, etc.) provided by a client.
In order to determine if one or more defined scaling criteria for the distributed execution of a program on a cluster are satisfied, as well as to otherwise track the distributed program execution, the DPE service may in some embodiments dynamically monitor the distributed program execution for some or all clusters. Such dynamic monitoring may include, for example, determining the status of execution of the program on each of the multiple computing nodes of a cluster, and may be performed in various manners in various embodiments. For example, in some embodiments, each cluster may include at least one administrative node selected to act as a master computing node for the cluster, and the master node may gather some types of status information regarding the ongoing distributed program execution by the cluster, such as from the execution jobs executing on other cluster computing nodes (e.g., a stage or phase of execution of an execution job, such as with respect to particular operations that are performed; an estimate of the amount of execution that has been performed and/or is remaining, such as measured by time or a percentage completeness; etc.), and if so the DPE service may automatically obtain some or all of that status information from the master node. In other embodiments, the DPE service may automatically gather other types of status information, such as directly from execution jobs executing on the cluster computing nodes, by interacting with manager modules of the DPE service that are local to various of the cluster computing nodes to determine status information for that computing node, etc. Furthermore, in at least some embodiments, the dynamic monitoring may include automatically gathering information about various types of resource usage by the distributed execution of a program on a cluster, such as resource usage specific to one or more particular cluster computing nodes that execute the program and/or aggregate resource usage from the distributed execution of the program across the entire cluster of computing nodes. The types of resource usage that are monitored and measured may vary in various embodiments, such as to include one or more of the following non-exclusive list, and may further be measured in absolute terms (e.g., a measured quantity of use) and/or in relative terms (e.g., a percentage used of the total available, to reflect the difference between an amount used by one program and the amount used by another program, etc.): network bandwidth capacity used, such as between two or more computing nodes of the cluster or more generally for any network resources used by the DPE service; disk I/O (“input/output”) capacity used for a particular cluster computing node and/or for a particular hard disk or other storage device used by one or more cluster computing nodes; amount of volatile or non-volatile memory used; amount of non-volatile storage used; amount of CPU cycles used or other measure of CPU utilization; bus bandwidth capacity specific to a particular cluster computing node; etc. In addition, in at least some embodiments, the dynamic monitoring may further include automatically determining whether the execution of one or more programs by the DPE service is contributing to a bottleneck with respect to access of one or more types of computing resources for other programs, such as for other programs of the DPE service. Such bottleneck detection may be performed in various manners, including by detecting when usage of particular computing resources rises above predefined thresholds, by detecting when performance of one or more other programs are having their execution delayed or otherwise hindered due to lack of available computing resources, etc. Additional details related to dynamically monitoring the ongoing distributed execution of a program on a cluster of multiple computing nodes are included below.
In addition, the dynamic modifying of the ongoing distributed execution of a program on a cluster of multiple computing nodes may be performed in various manners in various embodiments, including in some embodiments and situations based on information obtained from dynamic monitoring activities (e.g., to reflect defined scaling criteria that are satisfied, to reduce or eliminate bottlenecks, etc.). As previously noted, in some embodiments and for some types of programs, the dynamic modifying may include automatically scaling a cluster being used for distributed execution of a program while the distributed execution is ongoing, such as to expand the cluster during ongoing execution by adding one or more additional computing nodes and/or to shrink the cluster during ongoing execution by removing one or more of the computing nodes from the cluster. Cluster expansion may be performed, for example, to enable program execution to complete sooner, such as if execution on one or more cluster computing nodes is taking longer than expected, if execution of the program is being hindered by lack of sufficient computing resources and the additional computing nodes will provide access to additional computing resources that were lacking, if a master node or other cluster computing node has failed or otherwise become unavailable and the additional computing node(s) are configured to automatically take the place of the unavailable computing nodes, etc. Cluster shrinking may be performed, for example, to more efficiently use resources, such as if the distributed program execution is progressing faster than expected, if one or more cluster computing nodes are using too many computing resources and those computing nodes are shut down to throttle the excess computing resource usage, if one or more cluster computing nodes are not currently being used (e.g., have completed their portion of the distributed program execution and are removed from the cluster so as to be available for other uses and/or to prevent the ongoing distributed program execution from being responsible for ongoing fees for the computing node if it was part of the cluster), to remove all computing nodes from a cluster if a sufficient subset of the cluster computing nodes are not available for the ongoing execution (e.g., during an initial phase of the distributed program execution if a minimum percentage of cluster computing nodes and/or a minimum absolute quantity of cluster computing nodes have not completed their initialization and begun program execution within a predetermined period of time), etc.
Furthermore, in at least some embodiments, the dynamic modifying of the ongoing distributed execution of a program on a cluster of multiple computing nodes may include actions other than dynamic scaling of the cluster. For example, the dynamic modifying of the distributed execution of a program may include replacing computing nodes in the cluster that is executing the program with other computing nodes that have different resource configurations and/or capabilities, may include changing a particular use of one or more computing nodes that are currently in a cluster (e.g., switching a particular computing node between use as a core node and as an auxiliary node), etc. More generally, the dynamic modifying of the ongoing distributed execution of a program on a cluster may include otherwise automatically adjusting resource usage by the distributed program execution. For example, in at least some embodiments, the usage of one or more types of resources by one or more cluster computing nodes may be increased or decreased in various manners, such as by interacting with a module of the DPE service that is local to those cluster computing nodes to temporarily or permanently expand or restrict access to one or more types of computing resources by the execution jobs of the program being executed on those computing nodes (e.g., to limit network bandwidth usage by restricting how many communications are allowed to be sent over the network on behalf of the program; to expand storage space available to the program by changing an amount of storage allocated to the program and/or by reducing the amount of storage on a shared storage device that is being used by one or more other programs; etc.). In addition, in at least some embodiments, resource usage by one or more cluster computing nodes for distributed execution of an indicated program may be modified in other manners, such as by directly interacting with the indicated program to indicate a change in resource usage limits that are in use by the indicated program, by reducing or expanding the amount of resource usage by one or more other programs that share one or more types of computing resources with the indicated program so as to correspondingly expand or reduce the amount of resources available to the indicated program, by moving portions of the distributed program execution within the computing nodes of the cluster (e.g., to balance computing resource usage if some cluster computing nodes are under-utilized with respect to one or more types of computing resources and other cluster computing nodes are over-utilized with respect to those types of computing resources, by moving computing-resource intensive portions of the distributed program execution to cluster computing nodes that are configured or otherwise specialized for that type of computing resource usage, etc.), by moving portions of the distributed program execution to different computing nodes outside the cluster (e.g., if the aggregate computing resource usage for distributed execution of an indicated program is high with respect to network bandwidth capacity but low with respect to other types of resource usage, changing the computing nodes of the cluster so that the total quantity stays the same but the new cluster computing nodes are located closer together within the network or are provided with access to network bandwidth that is not used by or is under-utilized by other programs), etc. Such resource usage modification may be performed for various reasons, and may in some situations include temporarily throttling usage of computing resources by the distributed program execution (e.g., if the distributed program execution is using more computing resources than allocated or otherwise expected, if one or more bottlenecks exist with respect to executing programs of other users), terminating or temporarily suspending execution of the program (e.g., if an insufficient quantity of computing nodes of the cluster are available to perform execution), etc. Additional details related to dynamically modifying the ongoing distributed execution of a program on a cluster of multiple computing nodes are included below.
As previously noted, the techniques may include managing the initial configuration to be used in the execution of an indicated program in various manners, including using configuration parameters such as a quantity of computing nodes and/or other measures of computing resources to be used for the executing. The distributed execution of a program may be initiated and configured in various manners in various embodiments, such as by a user interacting with an embodiment of a DPE service to request the execution of the program in a manner specified by the user. For example, the DPE service may provide a GUI (“graphical user interface”) that a remote user interactively uses to make the execution request (e.g., a Web-based GUI with which a user interacts via a client-side application, such as a Web browser, executing on a client device of the user), and/or the DPE service may provide one or more APIs (“application programming interfaces”) that enable a computing device and program of the user to programmatically interact with the DPE service to make the request (e.g., one or more APIs that are also used by the provided GUI). The user may specify various information as part of such a request, such as an indication of the program to execute (e.g., by supplying an executable copy of the program, by indicating a program previously registered by the user with the DPE service, by indicating a program made available by the DPE service for use by users, etc.), and an indication of input data for use by the executing program (e.g., by supplying the input data or by indicating an accessible location from which the input data may be obtained). An executable copy of a program may be supplied in various manners and formats, such as, for example, a Java ARchive (“JAR”) file.
In addition, the user may further specify other configuration parameters for the distributed program execution in at least some embodiments, such as one or more of the following: an indication of a quantity of computing nodes to use for the requested execution; an indication of one or more resource configuration types of computing node to use for the requested execution (e.g., if the DPE service provides different types of computing nodes with different capabilities, such as different amounts of memory, storage and/or processing power); defined scaling criteria for use in determining whether and how to dynamically modify the ongoing distributed execution of the program; one or more other execution criteria to use in performing the requested execution (e.g., a user-specified QoS, or Quality of Service, level associated with the requested execution; an indication of a time by which the requested execution is to be completed; etc.); information about a location or layout of some or all of the computing nodes to use for the requested execution, such as relative to each other, to indicated data and/or to some other location (e.g., to be within a specified degree of geographical or network distance), or instead in an absolute manner (e.g., at a particular data center or other geographical location, within the boundaries of a country or other indicated geographical area, etc.); access information for use in communicating with one or more of the computing nodes, such as an SSH (“secure shell”) key; configuration information for use in configuring a particular instance of the program for use with the requested execution; an indication of multiple execution jobs into which the indicated program execution is to be separated for parallel or other distributed execution, or instead an indication of how the DPE service is to automatically determine those multiple execution jobs (e.g., if the indicated program is designed to be separable in a defined manner into distinct execution jobs, such as based on an execution methodology used by or other design of the program); etc. More generally, in at least some embodiments, a user may be able to specify other more general high-level execution criteria (e.g., to complete execution as cheaply as possible within some indicated time period, to complete execution as quickly as possible with a specified maximum associated fee, to complete execution in a manner that attempts to optimize one or more other types of indicated factors, etc.), and the DPE service may automatically determine preferred or otherwise appropriate execution configuration parameters to use to satisfy those execution criteria. Furthermore, in at least some embodiments, the DPE service may further automatically determine some or all such configuration parameters to otherwise use for the distributed execution of a particular program, such as for use in warning a user if user-specified configuration parameters are sub-optimal or otherwise problematic (e.g., are insufficient to complete the execution by a desired time indicated by the user), or for otherwise recommending configuration parameters to the user. The automatic determining of such configuration parameters may be performed in various manners in various embodiments, such as based on the DPE service monitoring and assessing previous related program executions for various users that use differing configuration parameters (e.g., execution of the same program, such as for a program provided by the DPE service for use by users; execution of other programs of the same or similar type, such as that use the same design or execution methodology; etc.) in order to identify one or more preferred sets of configuration parameters for a particular program or particular program type. Additional details related to configuring the distributed execution of a program are included below.
The ongoing distributed execution of one or more programs for a user may also be tracked and modified in various manners in various embodiments, such as by a user interacting with an embodiment of a DPE service to modify ongoing distributed program execution in a manner specified by the user. For example, the DPE service may provide a GUI that a remote user may interactively use to view status information related to ongoing distributed program execution (e.g., based on dynamic monitoring of the ongoing distributed program execution that is performed by the DPE service, based on status information gathered by a master node that is controlling the program execution or otherwise provided by the program, etc.) and/or to make a distributed program execution modification request (whether the same GUI as used for configuring program execution or instead a distinct GUI), and/or may provide one or more APIs (“application programming interfaces”) that enable a computing device and program of the user to programmatically interact with the DPE service to obtain such tracked information and make such modification requests (e.g., one or more APIs that are also used by the provided GUI for use in modifying execution). Information that is provided to a user may include, for example, one or more of the following: information about current use of different types of computing nodes within a cluster, including information specific to core nodes and/or auxiliary nodes, information specific to computing nodes of one or more resource configuration types, etc.; information about computing nodes that are available to be used within a cluster, including information about computing nodes of one or more resource configuration types; etc. The types of distributed program execution modifications that may be initiated by a user may vary in various embodiments and situations, including to modify various previously specified configuration parameters for an distributed program execution (e.g., a quantity of computing nodes to use for the ongoing distributed execution), to suspend and optionally later resume some or all of the ongoing distributed execution, etc. Additional details related to modifying the ongoing distributed execution of a program are included below.
FIG. 1A is a network diagram that illustrates an example of a DPE service that manages distributed execution of programs for multiple users. For illustrative purposes, some examples and embodiments are described below in which specific types of management of distributed program execution are provided in specific manners. These examples are provided for illustrative purposes and are simplified for the sake of brevity, and it will be appreciated that the inventive techniques may be used in a wide variety of other situations, some of which are described in greater detail below. For example, while particular examples of how to dynamically scale clusters used for the ongoing distributed execution of programs are described, other types of activities may be performed in other manners in other embodiments. In addition, while in some embodiments users initiate the execution of indicated programs in a distributed manner and/or modify the ongoing distributed execution of indicated programs, in other embodiments an embodiment of the DPE service may automatically initiate the execution and/or modification of such indicated programs and/or may determine to execute a program indicated by a user in a distributed manner (e.g., without knowledge of the user). Furthermore, in some embodiments at least some of the described techniques may be used with at least some programs that are not executed in a distributed manner, such as to configure, monitor and/or modify execution of such a non-distributed program.
In the example of FIG. 1A, a number of users 140 are interacting over a network 100 with an illustrated embodiment of a Distributed Program Execution service that is implemented by one or more modules 110, such as to initiate distributed execution of programs on one or more computing nodes 120 that are available for executing programs of the users. The network 100 may have various forms, such as, for example, to be a publicly accessible network of linked networks, possibly operated by various distinct parties (e.g., the Internet). In other embodiments, the network 100 may be a private network, such as, for example, a corporate or university network that is wholly or partially inaccessible to non-privileged users. In still other embodiments, the network 100 may include one or more private networks with access to and/or from the Internet. In the illustrated embodiment, the DPE service modules 110 and the computing nodes 120 are provided by a DPE service provider 105 as part of an embodiment of a DPE service, as well as one or more optional other storage nodes 130, and the DPE service modules 110 may execute on one or more other computing systems (not shown).
In some embodiments, the illustrated computing nodes 120 are provided by the DPE service provider 105 for distributed execution of programs on behalf of the users, and may include multiple physical computing systems and/or multiple virtual machines that are hosted on one or more physical computing systems (e.g., as is described in more detail with respect to FIG. 1B for one example embodiment). Each of the computing nodes 120 has some amount of computing resources available for executing one or more programs, such as may be measured, for example, by a combination of one or more of processing capacity (e.g., number and/or size of processing units), memory capacity, storage capacity, disk I/O (“input/output”) capacity, etc., and other components (not shown) provided by the DPE service may provide other computing resources (e.g., network bandwidth capacity of one or more networks, additional storage capacity of network storage devices or other storage remote from particular computing nodes, etc.). In some embodiments, the DPE service provider 105 may provide preconfigured computing nodes, with each preconfigured computing node having similar and/or equivalent amounts of computing resources available for executing programs on behalf of users, while in other embodiments, the DPE service provider 105 may provide a selection of various different computing nodes, such as with different types or groups of computing nodes having varying amounts and/or types of computing resources (e.g., size, speed and/or type of processing units; number of processing units; amount of memory and/or storage; platform configuration, such as 32-bit or 64-bit; etc.). FIG. 2A provides additional details regarding an example embodiment in which the computing nodes 120 include computing nodes of multiple resource configuration types.
In the illustrated embodiment, the various users 140 may interact with the DPE service modules 110 to make requests and specify various information. Such user requests and specifications may be made at various times, such as when a user registers to use services of the DPE service and/or at later times. For example, the DPE service modules 110 may provide subscription and/or registration services to one or more users, such that a user may specify information related to one or more programs to execute on behalf of the user (e.g., programs, source code, network addressable locations of one or more programs, etc.), account information (e.g., user name, billing information, etc.), terms of use, etc. In some embodiments, after a user interacts with the DPE service modules 110 to subscribe and/or register for services, the user may be issued one or more identifiers (e.g., keys, tokens, user names, etc.) that are associated with the user and are to be used in conjunction with executing programs on behalf of the user.
In addition, the users may interact with the DPE service modules 110 to initiate and configure execution of programs in various ways in various embodiments, such as by specifying a quantity and/or resource configuration type of computing nodes for execution of programs, a minimum and/or maximum quantity of computing nodes to use, an initial configuration of core computing nodes and/or auxiliary computing nodes to use for a cluster, one or more defined scaling criteria for use in determining whether to perform subsequent dynamic scaling of the quantity of computing nodes in a cluster or other modification of the cluster computing nodes, a preferred execution time and/or period of execution, an expiration time for the program execution request, a selection of one of multiple priorities for the execution (e.g., with associated fees that increase with increased priority), information about one or more resource configuration types of computing nodes to use, etc. Furthermore, in some embodiments, a user may interact with the DPE service modules 110 to request immediate execution of one or more programs on a specified number of computing nodes and/or to schedule such execution at one or more future times, such that the DPE service modules 110 may initiate the requested execution on the specified number of computing nodes at a specified time or when one or more specified execution criteria are satisfied (e.g., when it is determined that a specified number of computing nodes are available).
In this illustrated embodiment, the DPE service provides a variety of functionality for managing distributed execution of programs for multiple users on the computing nodes 120. For example, as previously noted, a particular user may use a GUI or API provided by the modules 110 to submit a request for execution of an indicated program using indicated input data, optionally along with a variety of other types of configuration information. After the request for execution of the program is received, the DPE service modules 110 may select which of the available computing nodes 120 to use for the requested execution in various ways. For example, in some embodiments, the modules 110 may simply select an appropriate quantity of computing nodes from any of the available computing nodes with sufficient resources, such as, for example, by randomly selecting from a pool of available computing nodes. In other embodiments, one or more specific computing nodes may be selected on the basis of one or more other factors, such as, for example, a predicted length of and/or likelihood of continued availability of the one or more computing nodes, a physical proximity of the one or more specific computing nodes to one or more other computing nodes, a geographic location of the one or more specific computing nodes and/or of one or more other computing nodes, a resource configuration type of the computing nodes, etc. In addition, after the request is received, the modules 110 may determine whether to use the multiple selected computing nodes for a cluster as core computing nodes and/or auxiliary computing nodes, and may further determine how to separate the indicated program into multiple execution jobs to be executed on some or all of the multiple selected computing nodes, such as by using information supplied by the user and/or in an automatic manner based on previously obtained information about the design of the indicated program. Similarly, in at least some embodiments and situations, the modules 110 may determine how to separate the indicated input data into multiple subsets for use by the multiple execution jobs. For example, in some situations, each execution job may include executing a full copy of the indicated program but on a particular subset of input data, while the other execution jobs similarly execute the full program copy functionality on other input data subsets. Alternatively, in some situations, various execution jobs may perform different functions on a single common set of input data. The modules 110 may further determine which computing nodes of a cluster execute which execution jobs in various manners, including in some situations based on the location in which input data to be used by an execution job is stored. As one example, an execution job may preferably be executed on a core computing node that already stores some or all input data for the execution job in some embodiments. As another example, if the computing nodes of a cluster are located in multiple distinct geographical and/or network locations (e.g., in multiple distinct data centers), a particular execution job may in some embodiments preferably be executed on one of one or more computing nodes that are at a particular location that stores at least one copy of the input data to be used for the execution job.
As the execution jobs execute on the various computing nodes of a cluster, the execution jobs store various information locally on the computing nodes in at least some embodiments, including as part of a distributed storage system on multiple core computing nodes, as discussed in greater detail elsewhere. In addition, the DPE service may optionally provide one or more storage nodes 130 that are used by the DPE service to store information related to program execution and/or for other purposes, such as to provide a reliable backup copy of data in case one or more computing nodes of the cluster become unavailable. As discussed in greater detail elsewhere, such information stored on the storage nodes 130 may include status information regarding the intermediate state of partial execution of various execution jobs for various programs, and in some embodiments may optionally include output data that is generated by completed execution jobs.
In addition, as the execution jobs of a program execute in a distributed manner on the various computing nodes of a cluster for that program, the DPE service may automatically perform various actions to dynamically monitor and/or modify the ongoing distributed execution of the program, with FIGS. 2A-2D illustrating examples of types of dynamic monitoring and modifying that may occur in some situations. For example, as discussed in greater detail elsewhere, the dynamic modifying of the ongoing distributed execution of the program on the multiple computing nodes of the cluster may include optionally performing various types of changes in certain situations, and the DPE service modules 110 may select which types of actions to pursue in which situations (e.g., based on predefined scaling criteria specified generally for the DPE service, or defined scaling criteria specified specifically for the program being executed or client on whose behalf the program is being executed). For example, if the DPE service modules 110 automatically determine to dynamically add and/or remove computing nodes from the cluster, the DPE service modules 110 may further select which computing nodes to add or remove, such as based on whether core computing nodes and/or auxiliary computing nodes are in use in the cluster, and/or in a similar manner to the selections made initially by the modules 110 in selecting particular computing nodes for the cluster. In addition, if the DPE service modules 110 automatically determine to make other types of changes to the ongoing distributed program execution, the DPE service modules 110 may similarly determine which types of changes to make (e.g., how to reduce bottlenecks corresponding to resource usage of the distributed program execution by altering the distributed program execution in one or more ways, such as by altering which execution jobs and/or input data are used by particular computing nodes, throttling resource usage on some or all computing nodes of the cluster, stopping the distributed program execution if sufficient cluster computing nodes are not available, etc.). Additional details related to the dynamic monitoring and modifying of ongoing distributed program execution are described elsewhere.
Furthermore, as discussed in greater detail elsewhere, in some embodiments the modules 110 may provide indications to cause the intermediate state of partial execution of one or more execution jobs to be persistently stored before the partial execution of the execution job is temporarily terminated or otherwise suspended. Such intermediate state information for the partial execution may be stored in various manners remotely from the computing node on which the partial execution occurred, such as by copying such intermediate state information to one or more of the optional storage nodes 130 and/or by using one or more optional remote storage services 150 that are accessible over the network 100. In some embodiments, the modules 110 coordinate the storage of the intermediate state information from the computing node to the remote persistent storage location, such as by using information that the modules 110 track about the intermediate state of the partial execution, while in other embodiments the activities in performing the persistent storage of the intermediate state information may instead be performed by management software executing on the computing node to locally manage the execution of the execution job. Alternatively, if a particular executing execution job is able to store its own intermediate execution state, the modules 110 may instead notify the execution job to perform its own intermediate execution state storage actions before shutting down its own execution. After the intermediate state of partial execution of an execution job has been persistently stored and the partial execution has been terminated, the partial execution may be resumed from that suspended intermediate state at a later time, such as substantially immediately (e.g., if the execution of the execution job is being moved from a first computing node to a second computing node, as quickly as the intermediate state information may be stored and retrieved), or instead after a longer period of time (e.g., at a later scheduled time, a later time when one or more specified execution criteria are satisfied, etc.). At the time of execution resumption, the stored intermediate state information may be retrieved from the persistent storage location, and locally stored on or otherwise made available to the computing node on which the execution job execution is to resume, and may include storing the data in a distributed storage system provided using multiple core computing nodes of the cluster. In addition, the partial execution of the execution job may be resumed in various manners, such as by indicating to the execution job not to perform a subset of operations that were previously completed (e.g., if the execution job supports such functionality), by modifying the execution job to only perform a subset of the operations that were not previously completed, etc. Additional details related to the suspension and resumption of execution of execution jobs are described elsewhere.
FIG. 1B illustrates an embodiment in which a DPE service may be provided using one or more data centers that include multiple physical computing systems. In particular, FIG. 1B is a network diagram illustrating an example embodiment in which one or more DPE service modules 180 of a DPE service manage distributed execution of programs on behalf of users at an example data center 170. The example data center 170 is connected to the Internet 196 external to the data center 170, which in this example provides access to various external computing systems, such as computing systems 190 via private network 194 and other directly accessible computing systems 192. The private network 194 may be, for example, a corporate network that is wholly or partially inaccessible from non-privileged computing systems external to the private network 194. Computing systems 192 may include, for example, a home computing system that connects directly to the Internet (e.g., via a telephone or cable modem, a Digital Subscriber Line (“DSL”), etc.). In addition, one or more other data centers 198 are illustrated that are connected to data center 170 via the Internet 196 and may each include additional computing systems, such as may further be used by the DPE service in at least some embodiments. For example, the distributed execution of a particular program may include simultaneous and/or sequential execution using computing nodes at multiple data centers or other distinct geographical locations, including to select a particular location at which to execute an execution job in various manners (e.g., based at least in part on a location at which corresponding data is stored and/or at which one or more particular computing nodes of interest to be used are located), and to optionally move execution of an execution job from a computing node at one geographical location to a computing node at another geographical location.
The example data center 170 includes a number of physical host computing systems 175, physical computing systems 182, optional storage systems 160, and one or more DPE service modules 180 that provide an embodiment of the DPE service. In this example, host computing systems 175 each provide multiple virtual machines 177 and have a virtual machine (“VM”) manager module 179 to manage those virtual machines (e.g., a hypervisor or other virtual machine monitor), and some or all of the computing systems 182 may similarly have one or more such virtual machines and/or VM manager modules (not shown). Such virtual machines may each act as a computing node for use by the DPE service, and a VM manager module on a host computing system provides one example of a type of module that the DPE service may use to dynamically monitor the host computing system (e.g., to obtain status information about one or more of the virtual machine computing nodes hosted by that host computing system) and/or to dynamically modify ongoing distributed program execution on one or more of the virtual machine computing nodes hosted by that host computing system (e.g., by throttling computing resources used by one or more of the hosted virtual machine computing nodes, by changing computing resources allocated to or otherwise available to one or more of the hosted virtual machine computing nodes, etc.). Alternatively, in other embodiments, some or all of the physical host computing systems at the data center may not provide any virtual machines, such as to instead each act as a computing node that directly executes one or more programs on behalf of end user customers of the DPE service, and such other host computing systems may similarly execute a module of the DPE service that monitors and/or modifies distributed program execution in which that host computing system participates. In addition, in some embodiments, the physical host computing systems 175 and/or physical computing systems 182 may each include management software (e.g., a management module of the DPE service, such as part of or distinct from the VM manager modules) to manage the execution of execution jobs on the computing systems, whether as part of or instead distinct from the DPE service module that performs the dynamic monitoring and/or modifying. Furthermore, in some embodiments various of the computing systems 175 and 182 may have differing capabilities, may have different associated fees for use, may support different types of user programs (e.g., virtual machine software image instances of different sizes, or programs with different types of computing resource usage, such as differing patterns of I/O and memory access and network usage), etc. If so, one or more such factors may further be used as constraints and/or preferences regarding which computing systems to select for executing particular programs. The optional storage systems 160 may also have various forms, such as computing systems with attached storage (e.g., that may also be used as computing nodes at times), network storage devices that are not used as computing nodes, etc. The example data center 170 further includes an internal network 172 that may include multiple networking devices (not shown), such as switches, edge routers, and core routers, with computing systems 175 and 182, storage systems 160, and the DPE service modules 180 connected to the internal network 172.
The illustrated DPE service modules 180 perform at least some of the described techniques in order to manage distributed execution of programs using the computing systems 175 and 182 (and optionally other external computing systems), and to optionally persistently store at least some program execution results on storage systems 160. For example, the DPE service modules 180 may provide a GUI or other functionality that enables remote users to configure distributed program execution and/or to track and optionally modify ongoing distributed program execution, such as for users (not shown) of computing systems 190 or 192 or at one of the other data centers 198. When a particular computing node or system is selected to execute one or more execution jobs of a program, the DPE service modules 180 may in some embodiments initiate execution of the execution jobs by interacting with a VM manager module or other manager module that controls execution of programs for that selected computing node/system, or may alternatively directly execute the execution jobs on the selected computing node/system. The DPE service modules 180 may further in some embodiments take various actions to dynamically monitor and/or modify the ongoing distributed execution of various programs executing on the computing nodes of the data center 170 that are used by the DPE service. In addition, some of the computing systems 190 or 192 or at one of the other data centers 198 may be used to provide one or more network-accessible remote storage services (not shown) that are accessible by the DPE service and used to persistently store at least some intermediate results or other information.
It will be appreciated that the data center of FIG. 1B is provided for illustrative purposes only, and that an embodiment of a DPE service and other software execution services may be provided in other manners in other embodiments. For example, DPE service modules 180 may instead be provided using one or more other computing systems external to the data center 170, such as computing systems 190, 192 or at a data center 198. In addition, in at least some embodiments, the programs for which distributed execution is provided may include executable software images, such as virtual machine images that are bootable or otherwise loadable on one or more virtual machine computing nodes, and that each may include operating system software, software for one or more application programs, and/or configuration information, etc. At least some such programs may be stored by the DPE service and/or by users on the storage systems 160 and/or using a remote storage service, and if so are retrieved by or supplied to the DPE service when they are to be executed on behalf of a user or as otherwise initiated. Furthermore, while only a limited number of devices are illustrated in this example, it will be appreciated that in a typical arrangement, data center 170 may include hundreds or thousands of host computing systems such as those illustrated here, organized into a large number of distinct physical networks with a large number of networking devices (e.g., in a hierarchical manner).
As previously noted, FIGS. 2A-2D illustrate examples of types of dynamic monitoring and modifying that some embodiments of a DPE service may perform to manage the ongoing distributed execution of indicated programs.
In particular, FIG. 2A illustrates additional example information regarding using the computing nodes 120 of FIG. 1A to perform the distributed execution of one or more programs for one or more clients of a DPE service embodiment. In this example, the computing nodes 120 include at least one type 120a of computing nodes, and optionally include computing nodes of one or more additional distinct resource configuration types 120b-120n. Each resource configuration type may have one or more computing nodes of that type, with each of the computing nodes of that type having a configuration of computing resources that differs from computing nodes of other resource configuration types, as discussed in greater detail elsewhere. In addition, while not illustrated here, the available computing nodes 120 may further include computing nodes that differ in one or more manners other than their resource configuration, such as to have different associated costs, different conditions of use (e.g., a minimum period of time and/or other specified conditions under which the computing node will continue to be available for use as part of the cluster, or the absence of any such associated ongoing availability guarantees), etc.
In FIG. 2A, the computing nodes 120 are being used in multiple clusters 205, including an example cluster 205z that the DPE service uses to perform distributed execution of an example Program Z for example client User Z, as well as one or more other example clusters 205x. FIGS. 2B-2D provide further example details regarding the distributed execution of one or more such programs. In the example of FIG. 2A, the cluster 205z includes multiple core computing nodes 207z, one or more auxiliary computing nodes 208z, and one or more administrative computing nodes 206z, although other clusters may have other configurations, including example cluster 205x that currently does not include any auxiliary computing nodes 208z. The core computing nodes 207z together provide a distributed storage system 209z for use with cluster 205z, with the distributed storage system 209z in this example storing various input data 235 to be used in the distributed execution of Program Z by cluster 205z and optionally storing various output data 245 that is generated by the ongoing distributed execution of Program Z. While not illustrated here, the auxiliary computing nodes 208z and optionally zero or more of the core computing nodes 207z may each be executing one or more execution jobs for Program Z.
In addition, the administrative computing nodes 206z may include one or more master nodes that manage the distributed execution of Program Z using the core computing nodes 207z and auxiliary computing nodes 208z, such as with at least one such administrative computing node acting as a name node to manage where copies of particular pieces or groups of input data are stored, and with at least one such administrative computing node acting as a job tracker node to manage the execution of particular execution jobs on particular computing nodes. For example, a job tracker node may identify that a particular execution job is available to be executed, select a particular available core or auxiliary computing node to execute that execution job, and assign that selected node to perform that execution job using indicated data. That selected node may then interact with the name node to identify a location of the indicated data if needed (e.g., if the selected node does not already store that indicated data), obtain the indicated data from the identified location if needed (e.g., if the selected node does not already store that indicated data), optionally obtain execution code for the indicated execution job if needed (e.g., if the selected node does not already store that execution code), and initiate execution of the indicated execution job using the indicated data.
FIG. 2B illustrates various example status information 210 that corresponds to the ongoing distributed execution of an example program at a particular time, and in particular of Program Z on cluster 205z of FIG. 2A at Time 1. In the example of FIG. 2B, various example computing nodes of cluster 205z are participating in the distributed execution of Program Z, as discussed in greater detail with respect to FIG. 2C, and one or more other computing nodes (not shown) may also be part of the cluster and acting as master computing nodes to control various actions of other cluster computing nodes. The status information 210 may reflect status information that is gathered by automatic monitoring by an embodiment of the DPE service (not shown) and/or by one or more of the master computing nodes. The status information 210 may be stored and used in various manners, and in some embodiments may be used by the DPE service in automatically modifying the distributed execution of Program Z.
In the example of FIG. 2B, the status information 210 is displayed as part of a GUI screen 285 that also includes various user-selectable controls 220. Such a GUI may be displayed to, for example, a human operator user of the DPE service, and/or User Z of the DPE service who initiated the distributed execution of Program Z. In this example, the user-selectable controls include a “Modify” control 220a via which the user may supply instructions to modify the ongoing distributed execution of Program Z in one or more manners as specified by the user (e.g., to add or remove computing nodes from the cluster, to modify computing resource usage of Program Z, etc.). In addition, in this example, the user may use the “Suspend” control 220b to temporarily suspend the ongoing in-progress distributed execution of Program Z, the “Terminate” control 220c to permanently terminate the ongoing in-progress execution of Program Z, and the “Duplicate” control 220d to initiate execution of a new program by duplicating at least some of the specified configuration information of a selected program via control 220b. In some embodiments, other controls may be available, such as a “Resume” control (not shown) to resume the execution of a previously suspended program, whether immediately or at an indicated future time, or more detailed controls to control the dynamic scaling of the cluster (e.g., separate controls to increase or decrease the quantity of computing nodes in the cluster; controls that affect the use of core and auxiliary nodes, such as to select a particular type of node whose quantity will be modified or to more generally indicate whether a particular scaling operation is intended to be permanent or temporary; etc.). It will be appreciated that other types of controls may be displayed in other embodiments, and that controls may be displayed and used in various manners in various embodiments.
In this example, the status information 210 includes various execution state information regarding the distributed execution of Program Z, such as to track the status of execution of execution jobs on the multiple computing nodes used for the distributed execution. In particular, in this example, the example time of Time 1 reflects a time that is shortly after distributed execution of Program Z has been initiated (e.g., 10 minutes), and thus the distributed execution of Program Z is not yet fully using the cluster computing nodes. In particular, computing node Node D 207z-d has not yet begun executing any execution jobs for Program Z, such as if Node D is still being initialized for Program Z (e.g., is still obtaining input data to be used, is still obtaining software code corresponding to one or more execution jobs of Program Z to be executed on Node D, is still configuring the Program Z software code before execution begins, is still establishing access to the master node and/or to other cluster computing nodes, etc.), or has encountered one or more problems (e.g., a failure or other unavailability, a bottleneck caused by another executing program, etc.). Computing node Node E 208z-e is similarly not yet executing any execution jobs for Program Z, but has just completed its initialization process, and is ready to begin executing its allotment of Program Z execution jobs. The other 3 computing nodes 207z and 208z that are included in the initial cluster for Program Z have already begun their respective portions of the distributed execution of Program Z at Time 1, with those other nodes being Node A 208z-a, Node B 207z-b, and Node C 208z-c. In this example, nodes A, C and E are auxiliary computing nodes 208z and nodes B and D are core computing nodes 207z, although the distributed storage system 209z is not illustrated, and the local storage by each node of its corresponding input data 235 and output data 245 is shown.
In addition, in this example, each line or entry in the information 210 corresponds to the performance of a particular operation for a particular execution job on a particular computing node, with information being tracked that in this example includes an identification 210a of the computing node, of the execution job 210b, of the operation 210c, of the status of performance 210f of the operation, of input data 210d to be used by the operation, of output data 210e to be produced by the performance of the operation, and optionally of various other information 210g. Such other status information may include, for example, information about dependencies or other inter-relationships between operations (e.g., operation B cannot be executed until after operation A is completed, operations C and D are to be executed simultaneously, etc.), information about expected completion of performance of an operation being performed (e.g., an expected completion time, an expected amount of time until completion, a percentage completion of an operation, a percentage of the operation that remains to be performed, etc.), information about expected initiation of performance of operations that are not yet being performed, etc. Various other types of information may similarly be displayed for Program Z, such as information about a current stage or phase of the execution, about the one or more master nodes that control execution of the execution jobs on the various cluster computing nodes and that may optionally gather and store various status information for the distributed execution, a graphical depiction of some or all of the various multiple computing nodes, etc.
While not illustrated in this example, in some embodiments and situations, different users or other entities may be involved in different parts of the distributed execution of a program, such as to have a first user initiate distributed execution of a program, a second user initiate a first suspension of execution of that program, a third user initiate a first resumed execution of that program, etc. Such two or more different users may, for example, represent a single client, not represent the same client but be affiliated in one or more other manners (e.g., based on working together), have authorization that has been granted to perform specified actions for other users, etc.
In the example of FIG. 2B, the execution of an example execution job J-A has been initiated on computing node Node A. Execution job J-A includes operations to be performed in this example that include at least example operations A01, A02, A03, and A04, and the first four entries in the status information 210 correspond to these operations for this execution job and computing node. In this example, operations A01 and A02 have begun and are in progress, with operation A01 using input data D-A01 and with operation A02 using input data D-A02. The graphical indications of cluster computing nodes 207z and 208z are provided in FIG. 2B for illustrative purposes to indicate information about the current status of the computing nodes, but are not displayed as part of the GUI screen 285 in this example. In particular, the graphical display of Node A 208z-a indicates the input data D-A01 235a and D-A02 235b that are currently loaded on Node A and being used, as well as indications 245a and 245b of output data for operations A01 and A02 that are in the process of being produced. In particular, operation A01 will produce output data D-A11 245a, which operation A03 uses as input data—since that data D-A11 245a is not yet available, operation A03 is queued to be executed while Node A is waiting for that data to be available (and optionally for sufficient computing resources to be available on Node A to execute the operation). Similarly, operation A02 is in progress and is using input data D-A02 to eventually produce output data D-A12, and since operation A04 uses that output data D-A12 as input data, operation A04 is similarly queued and ready to be executed when its input data and Node A are available to perform it. Similar status information is illustrated for other computing nodes, execution jobs and operations.
FIG. 2C continues the example of FIG. 2B, and in particular illustrates the changing status of the distributed execution of Program Z over time. The left portion of FIG. 2C corresponds to Time 1, and thus the graphical depictions of the computing nodes 207z and 208z match those shown in FIG. 2B at the same time. As discussed in greater detail elsewhere, in some embodiments the distributed execution of Program Z may be stopped at Time 1 or a prior time, such as if the 3 example computing nodes that have begun executing portions of Program Z just prior to Time 1 (those being Node A, Node B and Node C) are not determined to be a sufficient quantity or percentage of the cluster computing nodes (e.g., less than 90% participating in the distributed execution of Program Z within 10 minutes of the Time 0 initialization time for the Program Z distributed execution).
In the illustrated example, however, the distributed execution of Program Z is not stopped (or is stopped but is later resumed or restarted prior to Time 2), and the status of the distributed execution of Program Z at Time 2 is illustrated in the center of FIG. 2C. In this example, the progression of the distributed execution on the various cluster computing nodes has progressed. For example, with respect to Node A, operation A01 has now been completed, as reflected by the output data D-A11 240a as being shown as now being stored on Node A, and further being used as input for the now in-progress performance of operation A03 that is in the process of generating additional output data D-A21 245k. Since input data D-A01 has now been used, it may optionally have been removed from Node A, and operation A02 is continuing to be performed and in the process of generating output data D-A12 245b. The other computing nodes have similarly progressed in their distributed execution of Program Z, including that Node D and Node E are both now participating in the distributed execution of Program Z.
However, some modifications have been automatically made to the ongoing distributed execution of Program Z since Time 1 in this example. In particular, the cluster has been dynamically scaled to increase the total quantity of cluster computing nodes by at least 1, with new auxiliary computing node Node F 208z-f being illustrated and in use at Time 2 as part of the distributed execution of Program Z. The dynamic scaling may have been initiated in various manners, such as by an explicit instruction received from User Z or by the satisfaction of one or more defined scaling criteria for the cluster. If one or more defined scaling criteria were used to initiate the dynamic scaling, the defined scaling criteria may, for example, have been satisfied based on the execution status of one or more particular nodes or based on the aggregate execution status of the cluster. In this example, Node C may have experienced slower performance than expected (e.g., based on Node C having less available computing resources as compared to other cluster computing nodes; based on a bottleneck being created on a host physical computing system, not shown, that provides Node C, such as by another computing node provided by that host physical computing system as part of the distributed execution of another program; etc.), and/or the overall distributed execution of Program Z may be taking longer than expected (e.g., based solely on the unexpected delay with respect to Node C, based on unexpected slowness of one or more cluster computing nodes other than Node C; etc.). If so, the DPE service may have proceeded to automatically add Node F to the cluster, and in this example has distributed a portion of the Program Z operations that were previously assigned to Node C to now be performed by Node F. In particular, Node C continues to perform the operation C01, as was previously occurring at Time 1, but operation C02 has been transferred to Node F and is currently being performed by Node F at Time 2 (as demonstrated by the input data D-C02 235f being loaded on Node F and the output data D-C12 245k being in the process of being generated on Node F by operation C02). Node F also in this example is executing one or more other operations that were not previously assigned to any of the cluster computing nodes at Time 1, such as operation F01 (not shown) that uses input data D-F01 235k and is in the process of generating output data D-F11 245f. 
FIG. 2C further illustrates the status of the distributed execution of Program Z at a later Time 3, which is illustrated on the right side of FIG. 2C. In the illustrated example, much of the distributed execution of Program Z has been completed, and dynamic scaling has been used to reduce the quantity of computing nodes in the cluster by Time 3. As with the dynamic scaling that occurred prior to Time 2, the later dynamic scaling may have been initiated in various manners, such as by an explicit instruction received from User Z or by the satisfaction of one or more defined scaling criteria for the cluster. In this example, Node A and Node C have completed the portions of the distributed execution assigned to them (both the initial assignments, and any later assignments) before Time 3, and are also auxiliary computing nodes 208z that are preferably selected for dynamic removal in lieu of any core computing nodes 207z. Accordingly, while other cluster computing nodes continue the ongoing distributed execution of Program Z, the DPE service has automatically selected Node A and Node C to be removed from the cluster. Thus, in this manner, the DPE service may automatically modify the ongoing distributed execution of Program Z and the corresponding cluster used for that distributed program execution at various times and for various reasons. Clusters may be dynamically scaled in various other manners and for various other reasons, as discussed elsewhere.
FIG. 2D continues the examples of FIGS. 2B and 2C, and in particular illustrates additional status information regarding the ongoing distributed execution of Program Z, as well as other programs by the DPE service. In this example, status information 290 and 291 is shown that indicates status at Time 2, such as may be automatically gathered by automatic monitoring activities of the DPE service. In addition, the status information 290 and 291, as well as other status information 292 and 293, may be part of a GUI screen 295 that is displayed to one or more users in a manner similar to that previously discussed with respect to FIG. 2B, although no user-selectable controls are illustrated in the example of FIG. 2D, and/or the various status information may be used internally by the DPE service as part of automatically determining whether to perform dynamic scaling for the distributed execution of Program Z, such as based on the satisfaction of one or more defined scaling criteria. While not illustrated in FIG. 2D, in some embodiments the status information that is displayed may further include a variety of types of information about different types of computing nodes used in a cluster or that are otherwise available (e.g., about core computing nodes versus auxiliary computing nodes of a cluster; about computing nodes of different resource configuration types in a cluster, optionally in a manner that is also specific to core computing nodes and auxiliary computing nodes; about computing nodes in a cluster that are available from different sources, such as with different associated prices and/or use conditions, optionally in a manner that is also specific to core computing nodes and auxiliary computing nodes; about computing nodes that are available to be added to a cluster, such as computing nodes of different resource configuration types and/or that are available from different sources; etc.), including to display such information about ongoing execution of a program on a cluster to a client associated with the cluster in order to enable the client to dynamically modify the ongoing execution of the program on the cluster.
In the example of FIG. 2D, various status information 290 has been monitored regarding the distributed execution of Program Z at Time 2, including various aggregate computing resource usage information. In particular, in this example, each line or entry in the information 290 corresponds to a particular one of the cluster computing nodes, with information being tracked that in this example includes an identification 290a of the computing node, of one or more corresponding execution jobs 290b being executed on that computing node, of the status of performance 290c of the execution job(s), and various computing resource usage information 290d-290h. The example computing resource usage information that is shown in this example includes a quantity 290d of disk I/O for an indicated hard disk that the computing node is using (e.g., an average over a prior period of time, a current point-in-time value, etc.) and a percentage 290e of the total disk I/O for that indicated hard disk that the computing node is using, a quantity 290f of network bandwidth I/O for an indicated local network that the computing node is using (e.g., an average over a prior period of time, a current point-in-time value, etc.) and a percentage 290g of the total network bandwidth capacity for that indicated network that the computing node is using, etc. Various other types of computing resource usage information 290h may similarly be shown, and it will be appreciated that the various types of computing resource usage information may be displayed in various manners in various embodiments.
In addition to the computing resource usage data for the distributed execution of Program Z that is shown for each of the cluster computing nodes, the bottom of the status information 290 also shows aggregate computing resource usage information for the entire distributed execution of Program Z. For example, the illustrated data includes a total quantity 290d of disk I/O used by all of the cluster computing nodes, an average percentage 290e of the total disk I/O used by all of the cluster computing nodes, a total quantity 290f of network bandwidth I/O used by all of the cluster computing nodes, and an average percentage 290g of the total network bandwidth capacity used by all of the cluster computing nodes. In this example, most of the hard disks and networks being used by the cluster computing nodes are shared computing resources used by other computing nodes (e.g., other computing nodes of the same cluster, other computing nodes of other clusters that are executing other programs, etc.), although example hard disk N used by Node E is not shared (“NSh”) by others (e.g., is a remote logical network disk that is used only by Node E), and thus in this example the usage of that non-shared computing resource is not included in the aggregate computing resource usage information. In other embodiments, all computing resources may be shared or may be not shared, and the aggregate information may or may not include both types of computing resource usage information.
In addition to the status information 290 illustrated for the ongoing distributed execution of Program Z, FIG. 2D also illustrates other status information 291 corresponding to the ongoing distributed execution of other programs of the DPE service, although only aggregate computing resource usage information is shown for these other example programs. Furthermore, FIG. 2D also illustrates various status information 292 from monitoring the total usage of networks of the DPE service by the various programs being executed, and may similarly include status information 293 from monitoring the total usage of hard disks by the various programs of the DPE service being executed, as well as optionally other types of computing resource usage.
The various status information of FIG. 2D may be used in various manners, including by the DPE service as part of automatically determining whether to modify ongoing distributed execution of one or more programs of the DPE service, such as in accordance with one or more defined scaling criteria for particular programs and their clusters. For example, with respect to the ongoing distributed execution of Program Z, the usage of disk J (by Node A, at 70% of the total disk I/O) and aggregate usage of disk L (by Nodes C and F, at an aggregate 95% of the total disk I/O) may exceed an allocation or other expected usage for shared disks, and thus may create a bottleneck for any other programs that are attempting to use those disks. As such, the DPE service may determine to take various actions, such as to throttle the usage of those disks by those computing nodes (e.g., of the usage by one or both of Nodes C and F of disk L), or to take other actions to accommodate the actual or potential bottleneck (e.g., temporarily prevent any other computing nodes from using disk L, so that the aggregate 95% total disk I/O that is being used by Program Z does not create any actual bottlenecks for other programs). In other embodiments and situations, the DPE service may not take action until an actual bottleneck arises—for example, if other computing nodes are not attempting to use 30% or more of the total disk I/O for disk J, then Node A's use of 70% of the total disk I/O may be allowed until additional I/O capacity of disk J is requested by other computing nodes. Similarly, with respect to network bandwidth usage, the aggregate use of network T by Nodes D and E is 80% of the total network bandwidth capacity, and another 10% is being used by one or more other programs (as shown in the I/O capacity 292a, I/O usage 292b and I/O % 292c of status information 292). Accordingly, such network T usage by Nodes D and E may be throttled due to the potential or actual bottleneck caused by the use of network T for the distributed execution of Program Z. As another alternative, one or both of Nodes D and E may be automatically determined by the DPE service to be replaced or supplemented by one or more other computing nodes to be added to the cluster for Program Z that are part of other local networks of the DPE service, such as based on network T having relatively low total bandwidth capacity compared to other networks of the DPE service (e.g., network S with ten times more bandwidth capacity and a current total bandwidth usage of 24%).
It will be appreciated that the illustrated and other types of status information may be automatically monitored by the DPE service in various manners, and may be automatically used by the DPE service in determine modifications to make to ongoing distributed execution of programs. In addition, it will be appreciated that the information in the examples of FIGS. 2A-2D has been provided for illustrative purposes only, and various details have been shown in an abstract manner or not illustrated for the sake of understanding. Furthermore, it will be appreciated that while only a limited number of computing nodes and execution jobs have been illustrated, in actual embodiments the actual quantities may be much larger, such as to include hundreds or thousands or millions of computing nodes and/or execution jobs.
As previously noted, the DPE service may provide various functionality to perform distributed execution of programs for users. For example, after program execution is requested or otherwise initiated, whether by a user or in another manner, that program execution may be separated into multiple execution jobs for parallel or other distributed execution in various manners in various embodiments. As previously noted, the program may be designed to be separable in a defined manner into distinct execution jobs (e.g., to support task-level parallelism), and if so a user may indicate how to generate multiple execution jobs and/or the DPE service may automatically generate the multiple execution jobs. Furthermore, some types of programs may perform various operations on each of a number of pieces of input data, and in such situations, data parallelism techniques may be used to separate the group of input data for use in the program execution into multiple subsets that are each supplied to a distinct execution job (e.g., with each execution job performing some or all of the same operations on the input data subset used for that execution job). As one simple example, a particular program execution may include searching a large number of Web pages for two particular terms (or alternatively indexing the Web pages for use in later searches), and the program execution may be separated into a large number of execution jobs that execute simultaneously in parallel to each search (or index) a distinct subset of the Web pages (e.g., a single Web page, or a small number of the Web pages) for one or both of the terms. Non-exclusive examples of types of programs that may be separated into multiple execution jobs (e.g., to support task parallelism and/or data parallelism) include the MapReduce program for processing and generating large data sets by performing at least a first phase of various map functions and a second phase of various reduce functions, the Hadoop program implementation of MapReduce execution methodology, the Hive data warehouse infrastructure that uses Hadoop, the Pig structured query language for use with HDFS (“Hadoop Distributed File System”) data, the HBase open-source distributed database, various types of image, video and speech processing, various types of analysis of and searching through textual data sets or other types of input data, etc. Additional details related to the MapReduce program are included in “MapReduce: Simplified Data Processing on Large Clusters” by Jeffrey Dean and Sanjay Ghemawat, December 2004, Proceedings of OSDI'04: Sixth Symposium on Operating System Design and Implementation, which is incorporated herein by reference in its entirety, and which is also available at the time of application filing at labs<dot>google<dot>com<slash>papers<slash>mapreduce-osdi04.pdf (where “<dot>” and “<slash>” are replaced with corresponding characters “.” and “/”).
In addition, in at least some embodiments, the dynamic monitoring of the ongoing distributed execution of a program may include monitoring some or all execution jobs for the program, such as to determine when particular execution jobs begin execution and complete execution. Such monitoring of the execution of execution jobs may provide various benefits, such as to determine when to later initiate execution of other execution jobs (e.g., if the output data generated by a first execution job is at least some of the input data for a second execution job, so as to assist in determining when to execute the second execution job), and/or to determine when all execution jobs of a program have been completed. Furthermore, in at least some embodiments, some or all execution jobs may each have multiple distinct operations (which also may be referred to as “tasks” in some situations) that are to be performed, such as in a sequential and/or parallel manner, and the monitoring or other tracking of the ongoing execution of such execution jobs may further include determining information about the status of the partial performance of some or all such operations, such as to reflect intermediate data that is generated by completed performance of some such operations. Such tracking of the performance of particular operations for an execution job may further provide various benefits, such as to enable the ongoing intermediate execution and data state from the partial execution of the execution job to be tracked and used, as described in greater detail below. The monitoring may include using a system manager module to initiate execution of execution jobs on particular computing nodes, and to subsequently obtain status information from the computing nodes (e.g., by the system manager module pulling status information from the computing nodes, such as by periodically requesting status information from each computing node, and/or by the computing nodes pushing status information to the system manager module, such as periodically or when particular events occur).
When executing an execution job for a program on a computing node, various information related to the execution may be stored in various manners. For example, when the execution is initiated, the input data to be used by the execution job may be locally stored on the computing node (e.g., temporarily on a local hard disk or other local storage device) to facilitate access to that input data during execution, and any software instructions to be executed for the execution job may similarly be locally stored on the computing node, such as if with one or both types of data being retrieved from a distributed storage system for a cluster that is executing the program. As one example, if a distributed program is being executed using an implementation of MapReduce execution methodology, the input data and/or output data used by a computing node may be stored on a local portion of a distributed HDFS storage system on that computing node. After the execution of the execution job of the program is completed, the local storage on the computing node may in some embodiments be erased or otherwise cleared after any output data from the execution is copied back to the distributed storage system and/or to a remote long-term storage location used by the DPE service, such as in preparation for or as part of initiating execution of another execution job on the computing node (e.g., another execution job of a different program for a different user). In other embodiments, the local storage on the computing node may instead be maintained even after the execution of an execution job is completed (e.g., until execution of the program is complete). Furthermore, in at least some embodiments, various intermediate output data and other intermediate results from the partial execution of an execution job on a computing node may be temporarily stored locally on the computing node during the execution, such as to correspond to output data produced by a subset of the operations of the execution job whose performance is completed, and/or to correspond to partial or incomplete output data produced by one or more operations whose performance has been initiated but not completed. In at least some embodiments in which a long-term storage location of the DPE service is used, such intermediate results are not stored on the DPE service's long-term storage location (e.g., to minimize execution delay and network traffic involved in copying such intermediate results to the DPE service's long-term storage location), while in other embodiments some or all such intermediate results may be stored on the DPE service's long-term storage location.
As one example of intermediate results, referring back to the prior simplified example of an execution job that involves searching through multiple Web pages for two terms, each operation of the execution job may correspond to searching through a single Web page for a single term, with the intermediate output data from performance of such an operation being information about any occurrences of that term in that Web page (e.g., a cumulative number of times that the term is located; information about each occurrence of the term in that Web page, such as its location in the Web page; etc.). Alternatively, as another example, a particular execution job may involve searching through a Web log or other transaction record that has numerous entries (e.g., with each line in the Web log representing an entry) for a particular term, and each operation of the execution job may involve searching a particular input data entry for that term, with the intermediate output data from performance of such an operation similarly including information about whether the input data entry includes the term.
By storing the output data from the completed execution of an execution job in the DPE service's long-term storage location, the availability of that output data may be maintained even if one or more particular computing nodes subsequently fail or otherwise become unavailable, such as if those computing nodes are core computing nodes whose failure affects the use of the distributed storage system in which they participate. However, if intermediate results from partial execution of an execution job are not stored on the DPE service's long-term storage location, a termination of the execution of that execution job before completion may result in those intermediate results being lost, such that the execution job would need to later be executed again from the beginning (e.g., to repeat performance of all operations of the execution job, even if some of the operations were previously completed). Accordingly, distributed execution of a program is managed by the DPE service in at least some embodiments in such a manner as to store and use such intermediate results from partial execution of an execution job that is temporarily terminated or otherwise suspended before completion, so that a later resumption of the execution of the execution job may resume at or near the intermediate point of partial execution before termination. For example, if a determination is made to terminate execution of one or more execution jobs of a program on one or more computing nodes before the execution of those execution jobs is complete, a module of the DPE service may initiate the persistent storage of the intermediate results from the partial execution of those execution jobs, such as at a location remote from those computing nodes. When the execution of those execution jobs is later resumed, whether on those same computing nodes or other computing nodes, the persistently stored intermediate results from the prior partial executions may be retrieved and used in the resumed execution in various ways. For example, if multiple operations of a particular terminated execution job had been completed before the termination, the intermediate results from the performance of those operations may be retrieved for the resumed execution, and those completed operations need not be performed again for the resumed execution.
The termination of partially completed execution jobs may be performed for various reasons in various embodiments. For example, in some embodiments a user who has requested execution of a program may request that the execution of some or all execution jobs for the program be suspended, such as for an indicated period of time or until the user later requests a resumption of the program suspension. In other embodiments, the DPE service may initiate the termination of the execution of one or more execution jobs of a program. For example, the execution of an execution job on a first computing node may be terminated and moved to another second computing node, such as if the first computing node is to be shut down for maintenance, is to be used for another execution job or other program (e.g., another execution job or other program with a higher priority), is being over-utilized, is showing signs of possible failure, is over-using one or more types of computing resources, etc. In addition, in a manner similar to that of the indicated user request, the DPE service may determine to suspend all execution of a program for a period of time.
In addition, as previously noted, in at least some embodiments, execution of an execution job that is automatically terminated may be automatically resumed at a later time by the DPE service. For example, in some such cases, the DPE service may continue to try to execute such an execution job until completion of the requested execution, until execution is cancelled or otherwise explicitly terminated by a user, until occurrence of a specified time (e.g., until occurrence of an expiration time, until occurrence of a cumulative execution time, etc), until occurrence of a specified number of executions, indefinitely, etc. In addition, in at least some such embodiments, at least some execution jobs that are automatically terminated may be automatically resumed on behalf of the user at a future time when a sufficient amount of program execution capacity again becomes available to continue the execution. Similarly, if the ongoing distributed execution of a program is stopped due to an insufficient quantity of computing nodes of a cluster being available to perform the distributed execution or otherwise having insufficient computing resources to perform the distributed execution, the DPE service may reschedule the distributed execution for a later time and/or automatically restart the distributed execution at a future time when a sufficient quantity of computing nodes or other sufficient amount of program execution capacity again becomes available to continue the execution.
As previously noted, various information may be locally stored on a computing node during execution of an execution job, and the locally stored information may be stored in various manners. For example, in some embodiments, a distributed file system or other distributed data store may be created on multiple core computing nodes of a cluster used for distributed execution of a program, with a particular core computing node's locally stored data being stored in the local portion of that distributed data store. Furthermore, if the distributed data store for a particular embodiment includes redundant data that allows for recovery of the data locally stored on a particular computing node that fails or otherwise becomes unavailable, then the availability of the output data from the execution of an execution job may be maintained in many situations for that embodiment even without the use of separate long-term storage for the DPE service. In other embodiments, some or all information may be stored in other manners, such as by not using a long-term storage location of the DPE service (e.g., by maintaining locally stored data on computing nodes until all execution for the program is completed) and/or by not using local storage on the computing nodes selected to assist in the distributed execution of a program (e.g., by storing any information that is not loaded in volatile memory on the computing node at a remote location, such as the DPE service's long-term storage location).
In addition, when intermediate results of partial execution on a computing node are persistently stored remotely from the computing node, the intermediate results may be stored in various manners. In some embodiments in which the DPE service uses a long-term storage location, the intermediate results may be stored in the DPE service's long-term storage location along with other completed results of execution jobs that have been completed. Alternatively, in some embodiments, the intermediate results for a particular computing node may be stored together, but in a manner distinct from the intermediate and/or completed results of other computing nodes. For example, in some embodiments, a remote logical storage volume may be created to mirror some or all of a local hard disk or other block data storage device for the computing node that was used to store the intermediate results, including a local portion of a distributed file system or other distributed data store. When the partial execution of the execution job for the computing node is later resumed, such a remote logical storage volume may be attached to the computing node on which the resumed execution is to occur, such as to allow the information in the attached logical storage volume to be copied to a physical block storage device of that computing node for use during the resumed execution, or the attached logical storage volume may instead be used during the resumed execution in lieu of any physical block storage device of that computing node. In some such embodiments in which logical storage volumes are available for use, the logical storage volumes may be created at the time of termination of an execution job on a computing node, while in other embodiments the logical storage volume for an execution job may be created at the beginning of the initial execution of the execution job on a computing node and used throughout the entire execution (e.g., in lieu of any physical block storage device of that computing node), even if the execution of the execution job is terminated and resumed one or more times.
Additional details related to the operation of examples of remote storage services that may be used to persistently store program state information and/or other information, including logical storage volumes, are available in U.S. patent application Ser. No. 12/188,943, filed Aug. 8, 2008 and entitled “Providing Executing Programs With Reliable Access To Non-Local Block Data Storage;” and in U.S. patent application Ser. No. 11/371,304, filed Mar. 8, 2006 and entitled “Distributed Storage System With Web Services Client Interface” and claiming priority benefit of U.S. Provisional Patent Application No. 60/754,726 filed Dec. 29, 2005, each of which is hereby incorporated by reference in its entirety. In addition, additional details related to example embodiments of executing different programs of different priorities at different times and to techniques for suspending and resuming distributed execution of programs are included in U.S. patent application Ser. No. 12/334,022, filed Dec. 12, 2008 and entitled “Managing Use Of Program Execution Capacity,” and in U.S. patent application Ser. No. 12/334,004, filed Dec. 12, 2008 and entitled “Saving Program Execution State,” each of which is hereby incorporated by reference in its entirety. Furthermore, additional details related to enabling users to configure and modify distributed program execution are included in U.S. patent application Ser. No. 12/415,649, filed Mar. 31, 2009 and entitled “Managing Distributed Execution Of Programs;” in U.S. patent application Ser. No. 12/415,725, filed Mar. 31, 2009 and entitled “Dynamically Modifying A Cluster Of Computing Nodes Used For Distributed Execution Of A Program;” and in U.S. patent application Ser. No. 12/415,773, filed Mar. 31, 2009 and entitled “Dynamically Monitoring And Modifying Distributed Execution Of Programs;” each of which is also hereby incorporated by reference in its entirety.
In addition, as previously discussed, the managing of distributed execution of programs may be performed in various manners in various embodiments. For example, the determination of which computing nodes to use for execution of a program may be made in a variety of ways, including based on any preferences and/or requirements specified in configuration information that accompanies initiation of program execution or otherwise specified for the program and/or associated user (e.g., at a time of registration, etc.). For example, if preferred and/or required resources for execution of a program are identified (e.g., memory and/or storage; CPU type, cycles or other performance metric; network capacity; platform type, etc.), the selection of appropriate computing nodes to use may be based at least in part on whether the computing nodes have sufficient resources available to satisfy those identified resources. In at least some situations, the initiation of the distributed execution of the indicated program on a cluster by the DPE service includes some or all of the following non-exclusive actions: selecting multiple computing nodes to be used as the cluster to perform the distributed execution of the indicated program; identifying one or more of the multiple nodes of the cluster to act as master nodes that control the execution of the program on the other nodes of the cluster; provisioning the multiple computing nodes of the cluster if needed to prepare them to receive software to be executed and input data to be used; obtaining the indicated input data to be used by the distributed execution of the indicated program; separating the obtained input data into multiple subsets that are each to be used on one of the multiple computing nodes of the cluster; separating the indicated program into multiple execution jobs to be executed on the multiple computing nodes of the cluster; for each of the multiple computing nodes, loading on the computing node software and optionally input data to be used for the distributed execution of the indicated program (e.g., software to execute at least one execution job for the computing node and a determined subset of the indicated input data to be used by the computing node); optionally configuring the loaded software on the various computing nodes (e.g., configuring the software loaded on the one or more master computing nodes to be able to use the other computing nodes of the cluster); establishing access controls for the multiple computing nodes of the cluster that enable the multiple computing nodes to inter-communicate as part of the executing of the indicated program; etc. Additional details related to executing and configuring programs to execute on a program execution service are included in pending U.S. patent application Ser. No. 11/395,463, filed Mar. 31, 2006 and entitled “Managing Execution of Programs by Multiple Computing Systems,” which is hereby incorporated by reference in its entirety.
In some embodiments, fees may be associated with the use of a DPE service, such that the DPE service may perform distributed execution of programs on behalf of a user in exchange for payment of one or more fees by that user. For example, in some embodiments, fees may be charged to a user based on an amount and/or type of distributed program execution capacity allocated for executing one or more programs on behalf of a user, such as based on one or more of the following non-exclusive list: a number of computing nodes in a cluster, a number of processing units, an amount of memory, an amount of storage, an amount of network resources, etc. In some embodiments, fees may be based on other factors, such as various characteristics of the computing resources used to execute programs, such as, for example, based on CPU capabilities or performance, platform type (e.g., 32-bit, 64-bit, etc.), etc. Fees may also be charged on the basis of a variety of use factors in some embodiments, such as a price per use of the service, a price per unit of time that computing services are used, a price per storage used, a price per data transferred in and/or out, etc. In at least some embodiments, a provider of a DPE service may offer one or more of various tiers, types and/or levels of services or functionality for distributed execution of programs on behalf of multiple users, and in some such embodiments, various fees may be associated with the various tiers, types and/or levels of services. Additional details related to various fees associated with a distributed program execution service are included in pending U.S. patent application Ser. No. 11/963,331, filed Dec. 21, 2007 and entitled “Providing Configurable Pricing for Execution of Software Images,” which is hereby incorporated by reference in its entirety.
In addition, as previously noted, in at least some embodiments the DPE service provides an API to enable users to programmatically configure the distributed execution of programs and to modify ongoing distributed program execution. The following include non-exclusive examples of functions that may be provided as part of such an API: describe-cluster; run-cluster; terminate-cluster; set-cluster-proxy; upload-mapped-jar; upload-data; start-program; cancel-program; and get-program-status, in which “jar” refers to a file containing the indicated program to be executed. Furthermore, in at least some embodiments users may be enabled to configure a variety of characteristics for their clusters, including, for example, a degree of replication regarding how many copies (if any) to maintain of intermediate data during program execution, memory allocation to be used for particular programs (e.g., for use with a Java virtual machine), a loglevel for which information is tracked during debugging, etc. It will be appreciated that an API may include other functionality and be defined in other manners in other embodiments, and that the various functions of the API may each have appropriate variables or parameters whose values are specified as part of invoking the function.
In addition, in at least some embodiments, the DPE service may provide other types of functionality in at least some situations. For example, a user may initiate the distributed execution of a first program on a cluster of multiple computing nodes, but may maintain the cluster of multiple computing nodes even after the distributed execution of the first program has ended. One reason that the user may maintain the cluster is to execute a distinct second program on the existing cluster after the first program has ended, such as a second program that uses the same or similar configuration (e.g., the same type of program but with a new input data set), or instead a second program that uses generated results or other output data from the execution of the first program as input data for the distributed execution of the second program. As another example, in some embodiments, a user may be allowed to specify input data for use in the distributed execution of a program that is not static, such as if the input data continues to expand or otherwise change while the program is executing—one example is a log file for a Web site or data that indicates ongoing transactions, with the distributed execution of the program analyzing each entry in the log or transaction data, such that the new log/transaction entries are analyzed as they are received (or later if the processing of the log/transaction data has not yet reached those new entries at the time of their receipt), and another example is a program performing transaction processing services for ongoing transactions. Furthermore, in some embodiments a user may specify one or more types of limits regarding the distributed execution of a program (e.g., an amount of execution time; a cost of execution; an amount of usage of one or more types of computing resources, such as memory, storage, disk I/O, network I/O; etc.), with various specified types of actions that the DPE service is to take if a specified limit is reached (e.g., to notify the user, to suspend or terminate execution of the program, to reduce usage of a type of resource corresponding to the limit, etc.).
Furthermore, various other types of functionality may be provided and used by a DPE service in various embodiments, as discussed in greater detail elsewhere.
FIG. 3 is a block diagram illustrating an example embodiment of a system suitable for performing techniques to manage distributed execution of programs. In particular, FIG. 3 illustrates a server computing system 300 suitable for executing an embodiment of a Distributed Program Execution system 340, as well as various user computing systems 350, computing nodes 360, and other computing systems 380. In the illustrated embodiment, the server computing system 300 has components that include a CPU 305, various I/O components 310, storage 320, and memory 330. The illustrated I/O components include a display 311, a network connection 312, a computer-readable media drive 313, and other I/O devices 315 (e.g., a keyboard, a mouse, speakers, etc.). In addition, the illustrated user computing systems 350 have components similar to those of server computing system 300, including a CPU 351, I/O components 352 (although particular components are not illustrated), storage 354, and memory 357. The other computing systems 380 and computing nodes 360 may also each include similar components to some or all of the components illustrated with respect to server computing system 300, but such components are not illustrated in this example for the sake of brevity. In addition, the computing nodes 360 may be of multiple types in at least some embodiments, including of multiple resource configuration types, as discussed in greater detail elsewhere.
An embodiment of the Distributed Program Execution system 340 is executing in memory 330, such as under control of CPU 305 as programmed with software instructions of the system 340, and it interacts with computing systems 350 and 380 and computing nodes 360 over the network 390 (e.g., via the Internet and/or the World Wide Web, via a private cellular network, etc.). In this example embodiment, the DPE system 340 includes functionality related to managing distributed execution of programs on computing nodes 360 by various users (not shown) who are interacting with user computing systems 350, such as in conjunction with a network-accessible DPE service provided by the DPE system 340. The other computing systems 350 and 380 and computing nodes 360 may be executing various software as part of interactions with the DPE system. For example, user computing systems 350 may each be executing a Web browser 358 or other software in memory 357, such as to interact with a User Interaction Manager module 342 of the DPE system 340 in order to configure and/or request execution of programs on behalf of the users of those systems on one or more computing nodes 360 in various ways, to track and optionally request modifications to ongoing distributed execution of programs, and/or to perform various other types of actions.
Various information related to the operation of the DPE system 340 may be stored in storage 320, such as information 322 related to the computing nodes used to execute particular programs, information 328 about clients of the distributed program execution service, information 324 that includes information about program execution (e.g., final execution results from program execution that has been completed, status information about the intermediate state of partial execution of various programs, etc.), user-specified and other configuration information 326 used to configure distributed execution of programs (e.g., specified execution configuration parameters, defined scaling criteria related to dynamic cluster modification, etc.), and information 329 regarding the status of resource usage by executing programs and indications of detected bottlenecks. As discussed elsewhere, at least some of the illustrated information may be stored in other manners, such as if some or all of the program execution information 324 is stored in a distributed storage system (not shown) provided using various of the computing nodes 360, whether instead of or in addition to storing that information on storage 320. In addition, various intermediate state information and other information may be persistently stored in various manners, as discussed in greater detail elsewhere, including on a distributed storage system provided using various of the computing nodes 360 and/or on storage 320 of server computing system 300. In addition, in some embodiments other storage systems may be used to provide long-term storage of information for some or all clusters, as described elsewhere, including by using local or remote other computing systems 380 and/or other computing nodes/systems or storage nodes/systems (not shown).
After the DPE system 340 receives requests (or other indications) to execute one or more programs on one or more computing nodes 360, along with specified configuration information, the DPE system 340 selects the computing nodes for the cluster that will perform the distributed execution of the one or more programs, determines whether to use the selected computing nodes as core nodes or auxiliary nodes for the cluster, and initiates execution of execution jobs of those programs on at least some of those computing nodes 360 of the cluster. In addition, the DPE system 340 may further interact with computing nodes 360 to temporarily terminate or otherwise suspend execution of execution jobs on the computing nodes and to resume previously terminated execution, such as in response to user instructions. The DPE system 340 may also dynamically monitor or otherwise interact with one or more of the computing nodes 360 to track use of those computing nodes, such as under control of one of the optional other modules 349 of DPE system 340, and may further dynamically modify the ongoing distributed execution of programs on the computing nodes 360, such as to dynamically scale the cluster of computing nodes under control of the Cluster Modification Manager module 347 of DPE system 340. In some embodiments, the modules 347 and 349 may interact in various manners, such as if the module 347 requests or otherwise obtains information from one or more of the modules 349, while in other embodiments one of the modules 349 may store monitored information as part of information 329 and/or 324, and the module 347 may retrieve and use such stored information as desired. Furthermore, in some embodiments the DPE system 340 may optionally include a Program Configuration Manager module 344 that uses information gathered from the monitoring of the distributed execution of various programs to facilitate configuring the distributed execution of other programs, such as by determining preferred execution configuration parameters for particular predetermined types of programs and/or by determining recommended execution configuration parameters for particular indicated programs, although in other embodiments the module 344 may not be provided. If present, the Program Configuration Manager module 344 may further interact with the User Interaction Manager module 342 in some situations, such as to provide determined configuration information to the module 344 for presentation to users, while in other embodiments such determined configuration information may be stored by module 344 as part of configuration information 326, and retrieved and used by module 342 from the stored configured information 326. Additional details related to these operations are included elsewhere.
The computing nodes 360 may have various forms in various embodiments, such as to include a number of physical computing systems and/or a number of virtual machines executing on one or more physical computing systems. In some embodiments, the server computing system 300 and computing nodes 360 may be part of a data center or other group of co-located computing systems, or may otherwise be computing nodes of a private network. In addition, in some embodiments, the DPE system 340 may interact with one or more other computing systems 380 to initiate, suspend or resume execution of one or more programs on those computing systems, such as if the computing systems 380 are provided by one or more third-party participants. As described elsewhere, the computing nodes 360 may be of multiple types in at least some embodiments, including of multiple resource configuration types and/or in multiple distinct locations, and may in some embodiments be available from various sources that have differing associated fees for use and/or associated use conditions.
It will be appreciated that computing systems 300, 350 and 380 and computing nodes 360 are merely illustrative and are not intended to limit the scope of the present invention. The computing systems and/or nodes may instead each include multiple interacting computing systems or devices, and the computing systems/nodes may be connected to other devices that are not illustrated, including through one or more networks such as the Internet, via the Web, or via private networks (e.g., mobile communication networks, etc.). More generally, a computing node or other computing system may comprise any combination of hardware or software that may interact and perform the described types of functionality, including without limitation desktop or other computers, database servers, network storage devices and other network devices, PDAs, cell phones, wireless phones, pagers, electronic organizers, Internet appliances, television-based systems (e.g., using set-top boxes and/or personal/digital video recorders), and various other consumer products that include appropriate communication capabilities. In addition, the functionality provided by the illustrated DPE system 340 may in some embodiments be distributed in additional modules. Similarly, in some embodiments some of the functionality of the DPE system 340 may not be provided and/or other additional functionality may be available.
It will also be appreciated that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software modules and/or systems may execute in memory on another device and communicate with the illustrated computing systems via inter-computer communication. Furthermore, in some embodiments, some or all of the systems and/or modules may be implemented or provided in other manners, such as by consisting of one or more means that are implemented at least partially in firmware and/or hardware (e.g., rather than as a means implemented in whole or in part by software instructions that configure a particular CPU or other processor), including, but not limited to, one or more application-specific integrated circuits (ASICs), standard integrated circuits, controllers (e.g., by executing appropriate instructions, and including microcontrollers and/or embedded controllers), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), etc. Some or all of the modules, systems and data structures may also be stored (e.g., as software instructions or structured data) on a non-transitory computer-readable storage medium, such as a hard disk, a memory, a network, or a portable media article to be read by an appropriate drive or via an appropriate connection. The systems, modules and data structures may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). Such computer program products may also take other forms in other embodiments. Accordingly, the present invention may be practiced with other computer system configurations.
FIGS. 4A-4C are a flow diagram of an example embodiment of a Distributed Program Execution Service routine 400. The routine may be provided by, for example, execution of the DPE service modules 110 and 180 of FIGS. 1A and 1B, respectively, the DPE system 340 of FIG. 3, and/or the DPE service (not shown) that performs the activities described with respect to FIGS. 2A-2D, such as to manage distributed execution of programs and perform dynamic scaling of particular clusters, as well as to perform other types of actions in some situations. In this illustrated embodiment, the routine 400 manages various aspects of use of a DPE service that performs distributed execution of programs on behalf of multiple users.
In the illustrated embodiment, the routine begins at block 405, where information related to distributed program execution is received. The routine continues to block 410 to determine the type of received information. If it is determined in block 410 that a request is received to initiate execution of a program, such as from a user, the routine continues to block 420 to execute an Obtain User-Specified Program Execution Configuration Information routine, with one example of such a routine being described in greater detail with respect to FIG. 5. After the program execution configuration information is obtained in block 420, the routine continues to block 430 to execute a Perform Distributed Program Execution routine, with one example of such a routine being described in greater detail with respect to FIG. 6. While the obtaining of program execution configuration information and performing of distributed program execution in blocks 420 and 430 are illustrated as being performed in a synchronous manner, such that the routine 400 does not perform other operations during those blocks, it will be appreciated that the routine may continue to perform other operations asynchronously and simultaneously with the actions of blocks 420 and 430, including to monitor and modify ongoing program execution with respect to those blocks, as well as to perform other actions with respect to executing other programs for other users, as described elsewhere.
If it was instead determined in block 410 that the information received in block 405 was a request to register a program for later use, such as from a user, the routine instead continues to block 450 to store information about the program, along with associated administrative information (e.g., information about the user who submitted the program; information about execution of the program, such as how to separate the program into multiple execution jobs, a type of the program, etc.; optionally information about input data to be used during later execution of the program; optionally defined scaling criteria for later use in determining whether to dynamically scale a cluster being used for distributed execution of the program, etc.). In some embodiments, such programs may be registered by users before they are used, such as to increase the speed of executing the program when such a program execution request is later received. Furthermore, in some embodiments, such a request to register a program may include a request to schedule later execution of the program, such as at an indicated time or when one or more indicated execution criteria are satisfied (e.g., when sufficient excess computing capacity of the DPE service is available to execute the program at a low priority).
If it is instead determined in block 410 that the information received in block 405 is status information related to execution of one or more execution jobs as part of distributed execution of a program, such as may be supplied by those execution job(s) or associated computing node(s) performing the execution (e.g., after being previously requested by the routine 400 as part of block 430), the routine continues to block 455 to update status information that is maintained by the routine 400 regarding the intermediate state of execution of that execution job and program. As discussed in greater detail elsewhere, the status information may include information about particular operations that have been initiated, completed, or are in progress, information about input data that has been used by the execution, information about output data that has been generated by completion of some or all operations, information about partial intermediate data that reflects ongoing execution of the execution job, etc.
If it is instead determined in block 410 that the information received in block 405 is an indication related to modifying the ongoing distributed execution of one or more programs, such as from a user who initiated that execution and/or as previously specified by the routine 400 with respect to blocks 441 or 490, the routine continues to block 460 to receive information related to the execution modification. In block 462, the routine then determines whether the request relates to a temporary termination or other suspension of one or more currently executing execution jobs. If so, the routine continues to block 467 to, for each of one or more execution jobs to be suspended, obtain information about the current intermediate state of the partial execution of the operations being performed for the execution job by its associated computing node and about the current data state for the execution job on the associated computing node, and initiate the storage of the intermediate state information on one or more storage volumes remote from the computing node that will persistently store the information for later use. As previously discussed, in some embodiments the suspension may include temporarily terminating all execution jobs currently being executed for a program, such as to temporarily suspend execution of the program. In addition, if the computing node includes management software to perform such intermediate state storage actions or if the execution job itself is configured to save its own intermediate state when instructed, the routine 400 may instead send a message to the computing node and/or execution job to initiate such storage and then shut down. Furthermore, previously saved status information about the execution job may in some situations be used to determine what intermediate state information is be stored, and any new information obtained in block 467 (e.g., by communicating with the computing node and/or execution job) may be used to update the status information for that execution job. After block 467, the routine continues to block 469 to optionally schedule a later resumption of the execution of some or all of the execution jobs from the stored intermediate state. For example, in situations in which one or more execution jobs are being moved from a first group or one or more computing nodes to a second group or one or more other computing nodes, the later scheduled resumption of the execution of those execution jobs may occur in a substantially immediate manner, such that a user may be unaware of the termination and resumption of execution or of the movement of the execution job between computing nodes. In addition, the scheduling of the later resumption may include initiating a new request to be received in block 405 at the time of the later resumption that will prompt resumption activities for those execution jobs.
If it was instead determined in block 462 that the request was not to perform suspension of one or more execution jobs, the routine continues to block 464 to determine whether the request is instead related to resuming execution of one or more previously suspended execution jobs. If so, the routine continues to block 465 to initiate the resumption of execution of each of one or more previously suspended execution jobs on a computing node, such as by using previously stored state information about the intermediate results from the previous partial execution of the execution job, or instead schedules a later such resumption of the execution job if so indicated in the information received in block 460.
If it is instead determined in block 464 that the request is not related to resuming execution of previously suspended execution jobs, the routine continues to perform blocks 470-480 related to dynamic scaling of a cluster, such as under control of the Cluster Modification Manager module 347 of FIG. 3. In particular, in block 470, the routine determines if the request is to dynamically scale a cluster by reducing the quantity of computing nodes in the cluster. If so, the routine continues to block 472 to perform the reduction by selecting one or more computing nodes and removing them from the cluster. In this illustrated embodiment, the routine selects to remove auxiliary nodes if they are available, and to remove core computing nodes otherwise, but in other embodiments may proceed in other manners (e.g., to not remove core nodes if sufficient auxiliary nodes are not available). In other embodiments, the request may include additional information related to how to perform the reduction, such as a type of auxiliary or core node to be selected for reduction, a resource configuration type of computing node to be selected for reduction, an indication that computing nodes of a particular source are to be selected, an indication of a particular geographical and/or network location of computing nodes that are to be selected, an indication to perform the reduction by removing one or more computing nodes that were previously temporarily added to the cluster, etc., and if so the routine may perform the reduction in accordance with the instructions. In addition, in some embodiments, an intermediate execution state may be saved for some or all nodes being removed (e.g., in a manner similar to that described with respect to block 467), such as to enable later completion of the execution jobs being performed on those removed computing nodes by resuming from the intermediate state on other computing nodes of the cluster, although in other embodiments those execution jobs may instead be later completed by restarting the execution jobs from the beginning on other computing nodes of the cluster.
If it is instead determined in block 470 that the request is not to reduce the quantity of computing nodes in a cluster, the routine continues instead to block 475 to determine if the request is to dynamically scale a cluster by increasing the quantity of computing nodes in the cluster. If so, the routine continues to blocks 477-479 to perform the increase by selecting a type of computing node to add and by adding one or more computing nodes of that type to the cluster. In particular, in the illustrated embodiment, the routine selects in block 477 whether to add core or auxiliary nodes to the cluster, such as based on whether the adding of the nodes is intended to be a permanent or temporary increase, respectively, and/or based on one or more other factors. In addition, in some embodiments the selection may include other determinations and/or be made in other manners, such as to select a resource configuration type to use for the nodes being added, to select a particular source of the computing nodes to add based on an associated fee and/or associated use conditions for nodes from that source, to select a particular geographical and/or network location of computing nodes to be added, etc. In some embodiments, the request may include additional information related to how to perform the increase, such as a type of auxiliary or core node to be selected for reduction, a resource configuration type of computing node to be selected for reduction, an indication of whether the increase is temporary or permanent, an indication of fee-related factors to use in selecting computing nodes to add, etc., and if so the routine may perform the increase in accordance with the instructions. In addition, in some embodiments, if one of the added computing nodes begins to perform an execution job that was previously partially completed (e.g., by a computing node removed in block 472), that computing node may obtain and use a previously saved intermediate execution state to enable completion of the execution job by resuming from the intermediate state. If it is instead determined in block 475 that the request is not to dynamically scale a cluster by increasing the quantity of computing nodes in the cluster, the routine continues instead to block 480 to optionally perform one or more other indicated actions related to dynamic scaling of one or more clusters, initiate the removal of one or more computing nodes from a cluster that were previously temporarily added for an indicated period of time or until other indicated conditions were satisfied.
If it instead determined in block 410 that the type of information received in block 405 is an indication to dynamically monitor one or more clusters (e.g., periodically or when triggered by a particular event), such as to determine whether any defined scaling criteria for the clusters are satisfied, and optionally with respect to the ongoing distributed execution of a particular indicated program or instead with respect to the ongoing distributed execution of some or all programs being executed by the DPE service, the routine continues to block 433. The routine retrieves information in block 433 related to any such defined scaling criteria for the one or more clusters being monitored, and then continues to block 435. In block 435, the routine gathers aggregate information regarding the usage of computing resources by the ongoing distributed execution of one or more programs on the one or more clusters, and optionally retrieves status information regarding that ongoing distributed execution of the one or more programs (e.g., status information previously received and stored with respect to block 455, status information that is dynamically obtained by interacting with some or all computing nodes of each cluster performing the distributed execution of one of the programs, etc.). As discussed elsewhere, the aggregate information regarding the usage of the computing resources may be obtained in various manners, including by interacting with some or all computing nodes of a cluster performing the distributed execution of a program to obtain information specific to those computing nodes, and then aggregating the various node-specific information. After block 435, the routine continues to block 438 to determine if the gathered aggregate computing resource usage information for the one or more programs indicates that any defined scaling criteria are satisfied, and in some embodiments may further be used in other manners, such as to determine if any computing resources of the DPE service are being over-utilized. Such over-utilization of computing resources by the ongoing distributed execution of the one or more programs may, for example, create a bottleneck for at least one of those one or more programs and/or for one or more other programs, and/or may be based on the one or more programs using more computing resources than are allocated to those programs or that are otherwise expected to be used by those one or more programs. After block 438, the routine continues to block 441 to, if any defined scaling criteria are determined to be satisfied (and/or if any over-utilization of computing resources is detected), take corresponding actions. If one or more defined scaling criteria for a particular cluster are determined to be satisfied, the actions in block 441 include initiating a request to perform corresponding dynamic scaling of the cluster, as described in greater details with respect to blocks 470-479. In some embodiments and situations, such actions may also include, for example, initiating throttling of the use of the computing resources by at least one of the one or more programs, and/or may include modifying the amount of computing resources available to those one or more programs (e.g., to increase an allocation of computing resources available to those one or more programs, such that the current computing resource usage does not exceed the increased allocation), whether on the current computing nodes of one or more clusters or by modifying the computing nodes of the one or more clusters.
If it instead determined in block 410 that the type of information received in block 405 is another type of request, the routine continues instead to block 485 to perform the other indicated request as appropriate. Such other requests may include, for example, administrative operations with respect to users, such as users registering with the DPE service, users checking account information or other information of the DPE service, users tracking ongoing execution of their programs (e.g., by receiving some or all information about the intermediate state or other status of one or more of the execution jobs for the program), users providing payment with respect to currently or previously requested program executions or other provided functionality, etc.
After blocks 430, 441, 450, 455, 465, 469, 472, 475, 479, 480, or 485, the routine continues to block 490 to optionally perform one or more other tasks. Such other tasks may include, for example, one or more of the following: the DPE service automatically initiating the monitoring of the execution of various programs, such as by sending requests for status information to computing nodes (e.g., periodically, when indicated execution criteria are satisfied, etc.) and/or initiating the monitoring described with respect to blocks 433-441; automatically determining to temporarily terminate execution of execution jobs and/or to resume previously terminated execution of execution jobs in various circumstances, such as at scheduled times, to accommodate moving execution jobs between computing nodes, to maintain requested QoS levels for execution of a program (e.g., by maintaining execution of execution jobs within a maximum proximity to each other and/or to input data being used by the execution jobs, by maintaining a minimum proximity of execution to each other to enhance availability and reliability in the event of failure of multiple computing nodes in a single geographical location, etc.), to manage under-utilization and over-utilization of computing nodes (e.g., by modifying clusters and/or computing resources available to clusters), etc. After block 490, the routine continues to block 495 to determine whether to continue, such as until an explicit indication to terminate is received (e.g., from an operator of the DPE service). If it is determined to continue, the routine returns to block 405, and if not continues to block 499 and ends.
FIG. 5 is a flow diagram of an example embodiment of an Obtain User-Specified Program Execution Configuration Information routine 500. The routine may be provided by, for example, execution of the User Interaction Manager module 342 of the DPE system 340 of FIG. 3, or otherwise by the DPE service modules 110 and 180 of FIGS. 1A and 1B, respectively, and may be initiated by block 420 of FIG. 4. The routine 500 interacts with users to determine configuration information to be used to execute indicated programs in a distributed manner on multiple computing nodes, including to determine various execution configuration parameters and/or defined scaling criteria related to later dynamic scaling to be performed.
The routine begins in block 505, where an indication is received on behalf of a user regarding configuration information to be specified by the user regarding distributed execution of an indicated program. If it is determined in block 505 that the received indication is received via an API of the DPE service, the routine continues to block 510 to obtain and stored program execution configuration information via one or more API function calls, and to optionally store and aggregate such information over multiple API function calls. After the various program execution configuration information has been obtained, and an instruction is received via the API to initiate distributed execution of the indicated program in accordance with the specified configuration information, the routine in block 510 continues to block 599 and returns, including providing an indication of that specified configuration information and initiation instruction.
If it is instead determined in block 505 that the received indication is not received via an API, such as via a user interaction with a previously provided GUI of the DPE service or instead via a user request to obtain access to such a GUI, the routine continues instead to block 515 to provide (or update as appropriate) a GUI of the DPE service for display to the user, with the initial GUI screen(s) being configured to obtain information about an indicated program to execute and about various program execution configuration information. In block 520, the routine then receives information from one or more interactions of the user with the displayed GUI that indicates the program to be executed and optionally various other user-specified configuration information. While not illustrated here, in some embodiments the routine may further provide information to at least some users about recommended defined scaling criteria for dynamic scaling (e.g., based on a type of the program to be performed, on indicated objectives of the user, etc.) and/or about other recommended execution configuration parameters for distributed execution of the indicated program. As described in greater detail elsewhere, the information about the recommended execution configuration parameters may be used in various manners and times in various embodiments, including for display to the user (e.g., for use as modifiable default values for the execution configuration parameters, for use in providing a warning about other user-specified execution configuration parameters, etc.). In addition, the recommended execution configuration parameters may be determined in various manners in various embodiments, as discussed elsewhere. After the various configuration information has been provided, the routine receives instructions from the user in block 540 to initiate the distributed execution of the indicated program in accordance with the specified configuration information, and continues to block 599 and returns, including providing an indication of that specified configuration information and initiation instruction.
While not illustrated here, it will be appreciated that in some embodiments a user may begin the interactions described with respect to FIG. 5, and then decide to explicitly cancel the interactions or otherwise fail to complete the interactions. In such situations, the routine may exit without providing an indication of the program execution initiation instruction (and optionally without any configuration information specified by the user before the cancellation/completion failure), and the routine 400 in FIG. 4 may instead determine to skip block 430 due to the lack of the program execution initiation instruction.
FIG. 6 is a flow diagram of an example embodiment of a Perform Distributed Program Execution routine 600. The routine may be provided by, for example, execution of the DPE service modules 110 and 180 of FIGS. 1A and 1B, respectively, and/or the DPE system 340 of FIG. 3, and may be initiated by block 430 of FIG. 4. The routine 600 performs operations to execute indicated programs in a distributed manner on multiple computing nodes in accordance with specified configuration information.
The routine begins in block 610, where it receives program execution configuration information for use in executing an indicated program, such as from the output of routine 500 of FIG. 5. After block 610, the routine continues to block 615 to determine a quantity of computing nodes to be used in a cluster for the program execution, such as is specified in the received execution configuration information, or otherwise automatically determined (e.g., based on preferred or default configuration information, a number of computing nodes that are currently available from the DPE service, a number of computing nodes to correspond to a number of execution jobs into which the program execution will be separated, an amount of fees paid by a user on whose behalf the request is made, etc.). In addition, the routine in block 615 may determine other information regarding the initiation of the distributed program execution, such as whether some/all of the cluster computing nodes are to be used as core nodes and/or as auxiliary nodes, one or more resource configuration types to use for the initial computing nodes, a particular source of the computing nodes to be used based on an associated fee and/or associated use conditions for nodes from that source, a particular geographical and/or network location of computing nodes to be used, etc. In block 620, the routine separates the program execution and any received input data into multiple execution jobs that each involves one or more operations to be performed. The actions in blocks 615 and 620 may be performed in various manners in various embodiments, as discussed in greater detail elsewhere. For example, the program execution separation may be performed in a manner specified in the program execution configuration information, in an automated manner based at least in part on the design of the program, etc. After block 620, the routine continues to block 625 to select the determined quantity of computing nodes for use in distributed execution of the program based on the information determined in block 615, and in block 630 initiates the execution of at least some of the execution jobs on the selected nodes. As discussed in greater detail elsewhere, in some embodiments a user may specify a variety of other types of information, such as may be received as part of the configuration information received in block 610 and used as part of the actions in blocks 615-630.
After block 630, the routine continues to block 635 to perform various continuing activities over time as part of performing the distributed execution of the program on the cluster of computing nodes. Such continuing activities may include determining at a later time that there are more execution jobs available to be executed at that time, and initiating execution of one or more of those execution jobs on currently available computing nodes of the cluster (e.g., based on the computing nodes of the cluster after any prior dynamic scaling has been performed, and which are not otherwise currently occupied in the distributed execution of the program), such as if those execution jobs had been waiting for output data from one or more of the completed execution jobs, or instead if there had initially been more execution jobs than available computing nodes. Such continuing activities may also include waiting for execution jobs to complete and to optionally provide corresponding output data, such as may be used as input data to other execution jobs and/or may be used as part or all of the final results for the execution of the program. In some embodiments, the computing nodes may supply such output information back to the routine 400, such as for storage in a long-term storage location of the DPE service, while in other embodiments the output results may instead be stored on the computing nodes (e.g., as part of a distributed storage system on multiple core computing nodes), and/or stored by the computing nodes on one or more long-term storage locations remote from the computing nodes. In addition, the continuing activities may include dynamically scaling the cluster or performing other cluster modifications, such as in response to user instructions or satisfaction of defined scaling criteria, as described in greater detail with respect to blocks 460-480 of FIG. 4C. In the illustrated embodiment, blocks 630-655 are illustrated as being performed in a synchronous manner in which the routine 600 waits for execution jobs to complete before performing other actions. It will be appreciated that in other embodiments the routine 600 may operate in other manners, such as in an asynchronous manner to perform other actions with respect to executing the current program and/or to executing other programs for other users. In addition, it will be appreciated that in some situations errors may occur that cause one or more execution jobs to fail to complete, such as due to problems with the computing node on which the execution job is being performed, due to a network connection with the computing node, due to an error in the software corresponding to performing the execution job, due to problems with input data to be used for the performance of the execution job, etc. In such situations, the routine may take various actions to correct the errors (e.g., by transferring the execution job to another computing node), but if an irreversible error occurs, the routine may terminate the further distributed execution of the program or may instead attempt to complete as much of the distributed execution of the program as possible and provide incomplete final results along with an indication that the program executed is completed with errors.
After all of the execution jobs have completed in block 635, the routine continues to block 685 to produce final execution results for the program, and to optionally store those final results and/or provide them to the user. The final execution results may be generated or otherwise produced in various manners in various embodiments, such as by combining output results from multiple execution jobs in various ways, selecting the output results from a single execution job to use, etc. After block 685, the routine continues to block 699 and returns.
FIG. 7 is a flow diagram of an example of a Computing Node Manager routine 700. The routine may be provided by, for example, execution of module 179 of FIG. 1B, or of other management software executing on computing nodes 120 of FIG. 1A, computing systems 182 of FIG. 1B, computing nodes 360 of FIG. 3, etc. In the illustrated embodiment, the management software on a computing node manages some aspects of the execution of execution jobs on the computing node, while in other embodiments some or all of the functionality described with respect to FIG. 7 may instead be performed by the routine 400 of FIGS. 4A-4C, or instead by an execution job that is being executed on the computing node.
In the illustrated embodiment, the routine begins at block 705, where an indication is received related to the execution of one or more execution jobs on the computing node. The routine continues to block 710 to determine whether the indication is to initiate execution of an indicated execution job. If so, the routine continues to block 713 to obtain the input data to be used for the indicated execution job and to store it locally, and to determine the multiple operations to be performed for the execution job (e.g., based on the information received about the execution job in block 705 or that is otherwise retrieved from an external source). The input data to be used may be obtained in various manners, such as by being received in block 705, already being available on local storage (e.g., if the computing node is a core node whose local portion of the distributed storage system stores that input data), being retrieved from another computing node that is a core computing node (e.g., if the current computing node is an auxiliary node or is a core node whose local portion of the distributed storage system does not store that input data), etc. After block 713, the routine continues to block 715 to select the next operation to be performed, beginning with the first. Blocks 715-740 are illustrated in this example embodiment as being performed in a serial manner, such that each operation is individually performed in a synchronous manner before the next operation is initiated, although it will be appreciated that in other embodiments the operations may be performed in other manners, such as to execute some or all of the operations in parallel and/or in an asynchronous manner.
After block 715, the routine continues to block 720 to send a status message to the routine 400 indicating that the execution of the selected operation has begun, and in block 725 initiates the performance of the operation. In block 730, the routine waits for the completion of the performance of the operation, and optionally locally stores any intermediate results produced by the operation performance. In block 735, the routine then sends another status message to the routine 400 indicating that the performance of the operation is completed. In block 740, the routine then determines whether there are more operations to be performed, and if so returns to block 715.
If was instead determined in block 710 that the received indication in block 705 was not to execute an execution job, the routine continues to block 745 to determine whether the received indication in block 705 is to perform one or more activities related to participation in a distributed storage system, although such activities may be performed only for core nodes in at least some embodiments. If so, the routine continues to block 750 to take actions to perform one or more such activities. The actions may include storing indicated data in a local portion of the distributed storage system and/or retrieving and providing such locally stored data to a requester (e.g., to another computing node with respect to block 713 of a routine performed for that other computing node), and may further include taking various activities to establish the participation of the computing node in the distributed storage system when the use of the cluster is first initiated.
If was instead determined in block 745 that the received indication in block 705 was not to participate in the distributed storage system for the cluster, the routine continues instead to block 785 to perform one or more other indicated operations as appropriate. For example, the information received in block 705 may be a request for status information from the routine 400, and if so block 785 may obtain and provide that status information to the routine 400. Alternatively, the information in block 705 may be an indication to terminate execution of the execution job, and the actions performed in block 785 may include corresponding actions (e.g., to clear intermediate state information that was temporarily stored on the computing node, such as after that information has been persistently stored elsewhere). In addition, actions performed with respect to block 785 may include a request from the routine 400 to initiate such persistent storage of intermediate state from partial execution of operations for a currently executing execution job, and if so the actions in block 785 may include performing such actions (whether immediately or instead after a short time to allow completion of performance of one or more operations). Similarly, actions performed with respect to block 785 may include a request from the routine 400 to throttle or otherwise modify computing resource usage by the computing node, and if so the actions in block 785 may include performing such actions. Furthermore, in some embodiments and situations, different execution jobs may coordinate in various manners, such as by exchanging information of interest, and the information in block 705 may be such information from another execution job of the program or a request from such other execution job for information from the current execution job.
After blocks 750 or 785, or if it is instead determined in block 740 that there are no more operations to be performed, the routine continues to block 790 to optionally perform one or more other tasks, such as to coordinate with other execution jobs of the program if appropriate, to take administrative actions as part of executing the execution job, etc. After block 790, the routine continues to block 795 to determine whether to continue, such as until an explicit indication to terminate is received (e.g., from the routine 400 or from a human operator of the DPE service). If it is determined to continue, the routine returns to block 705, and if not continues to block 799 and ends.
It will be appreciated that in some embodiments the functionality provided by the routines discussed above may be provided in alternative ways, such as being split among more routines or consolidated into fewer routines. Similarly, in some embodiments illustrated routines may provide more or less functionality than is described, such as when other illustrated routines instead lack or include such functionality respectively, or when the amount of functionality that is provided is altered. In addition, while various operations may be illustrated as being performed in a particular manner (e.g., in serial or in parallel) and/or in a particular order, those skilled in the art will appreciate that in other embodiments the operations may be performed in other orders and in other manners. Those skilled in the art will also appreciate that the data structures discussed above may be structured in different manners, such as by having a single data structure split into multiple data structures or by having multiple data structures consolidated into a single data structure. Similarly, in some embodiments illustrated data structures may store more or less information than is described, such as when other illustrated data structures instead lack or include such information respectively, or when the amount or types of information that is stored is altered.
From the foregoing it will be appreciated that, although specific embodiments have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims and the elements recited therein. In addition, while certain aspects of the invention are presented below in certain claim forms, the inventors contemplate the various aspects of the invention in any available claim form. For example, while only some aspects of the invention may currently be recited as being embodied in a computer-readable medium, other aspects may likewise be so embodied.

## Claims

1. A computer-implemented method comprising:
receiving configuration information regarding execution of an indicated program in a distributed manner that includes executing a plurality of jobs of the indicated program, the configuration information being received by one or more computing systems configured to provide a distributed program execution service that performs distributed execution of programs for clients using a plurality of configurable computing nodes;
automatically determining a subset of multiple of the plurality of configurable computing nodes to be used for the execution of the indicated program in accordance with the received configuration information, the multiple computing nodes of the determined subset including a first group of one or more computing nodes to act as core computing nodes that each participate in a distributed storage system storing information used in the execution of the indicated program, the multiple computing nodes of the determined subset further including a second group of one or more computing nodes to act as auxiliary computing nodes that do not participate in the distributed storage system, the automatic determining of the subset being performed by the one or more configured computing systems;
initiating the execution of the indicated program in the distributed manner on the multiple computing nodes at a first time by executing one or more of the plurality of jobs of the indicated program on each of the multiple computing nodes, the initiating of the execution of the indicated program being performed by the one or more configured computing systems; and
at a second time subsequent to the first time and during the execution of the indicated program, determining to reduce a quantity of the multiple computing nodes that are used for ongoing execution of the indicated program, and automatically reducing the quantity of the multiple computing nodes by initiating removal of at least one of the auxiliary computing nodes of the second group without removing any of the core computing nodes of the first group, the automatic reducing of the quantity of the multiple computing nodes being performed by the one or more configured computing systems.

2. The method of claim 1 wherein the determined subset of multiple computing nodes are part of a cluster that is created for use in the execution of the indicated program on behalf of a first client from whom the configuration information is received, and wherein the determining to reduce the quantity of the multiple computing nodes is performed based on one of an instruction received at the second time from the first client and of an automated determination at the second time by the one or more configured computing systems that one or more scaling criteria defined by the first client prior to the second time for the cluster are satisfied at the second time.

3. The method of claim 2 wherein the determining to reduce the quantity of the multiple computing nodes is performed based on the automated determination at the second time by the one or more configured computing systems that the one or more defined scaling criteria are satisfied at the second time, and wherein the one or more defined scaling criteria are satisfied at the second time based at least in part on a stage of the execution of the indicated program that is specified by at least one of the one or more defined scaling criteria.

4. The method of claim 2 wherein the determining to reduce the quantity of the multiple computing nodes is performed based on the automated determination at the second time by the one or more configured computing systems that the one or more defined scaling criteria are satisfied at the second time, and wherein the one or more defined scaling criteria are satisfied at the second time based at least in part on a monitored state of use of computing resources by the execution of the indicated program that is specified by at least one of the one or more defined scaling criteria.

5. The method of claim 1 wherein the method further comprises, at a third time subsequent to the first time and during the execution of the indicated program, automatically modifying at the third time the quantity of the multiple computing nodes that are used for the ongoing execution of the indicated program, the automatic modifying being performed by the one or more configured computing systems and including at least one of automatically removing at least one of the auxiliary computing nodes of the second group, automatically adding at least one computing node to the auxiliary computing nodes of the second group, automatically removing at least one of the core computing nodes of the first group, and automatically adding at least one computing node to the core computing nodes of the first group.

6. The method of claim 5 wherein the plurality of configurable computing nodes include computing nodes of multiple distinct resource configuration types that each have a distinct configuration of one or more computing resources, and wherein the automatically modifying at the third time of the quantity of the multiple computing nodes includes selecting one of the multiple distinct resource configuration types and performing one or more modifications involving one or more computing nodes of the selected one resource configuration type.

7. The method of claim 1 wherein the distributed storage system is a distributed file system, wherein each of core computing nodes stores a portion of the distributed file system on local storage of that core computing node, wherein a first of the core computing nodes stores a first and second subset of input data for the indicated program in the portion of the distributed file system on the first core computing node, wherein the executing of the one or more jobs of the indicated program on the first core computing node includes selecting a first execution job for the first core computing node based on the first execution job using the first subset of input data that is stored by the first core computing node and includes selecting a second execution job that uses the second subset of input data for a first of the auxiliary computing nodes, and wherein the executing of the second execution job by the first auxiliary computing node includes obtaining the second subset of input data from the first core computing node.

8. The method of claim 7 wherein the determined subset of multiple computing nodes include computing nodes at multiple distinct geographical locations, wherein the first core computing node and the first auxiliary computing node are co-located at a first of the multiple geographical locations, and wherein the selecting of the first auxiliary computing node for the second execution job that uses the second subset of input data is based at least in part of the first auxiliary computing node being co-located with the first core computing node that stores the second subset of input data.

9. The method of claim 1 wherein the determined subset of multiple computing nodes are part of a cluster that is created for use in the execution of the indicated program on behalf of a first client, and wherein the method further comprises monitoring ongoing execution of the indicated program on the cluster to generate status information related to the ongoing execution, the generated status information including first status information for the first group of computing nodes acting as core computing nodes and including second status information for the second group of computing nodes acting as auxiliary computing nodes, and providing at least some of the generated first status information and generated second status information to the first client during the ongoing execution of the indicated program to enable the first client to track the ongoing execution with respect to the first and second groups of computing nodes.

10. The method of claim 1 wherein the indicated program is configured to perform one or more map functions on each of multiple input data subsets and to perform one or more reduce functions on results of the one or more map functions, wherein the method further comprises generating at least some of the plurality of jobs to each implement at least one of the map functions or at least one of the reduce functions and further comprises completing the execution of the plurality of jobs of the indicated program and further comprises providing final results from the execution to a first client who supplied the received configuration information, wherein the distributed program execution service provides the plurality of configurable computing nodes and uses virtualization technology such that the plurality of computing nodes include, for each of multiple physical computing systems, multiple virtual machines hosted by the physical computing system that are each able to execute at least one portion of a program, and wherein the multiple computing nodes on which the indicated program is executed are each a hosted virtual machine.

11. A non-transitory computer-readable medium whose contents configure a computing system to perform a method, the method comprising:
initiating execution of an indicated program in a distributed manner on a cluster of multiple computing nodes at a first time;
at a second time subsequent to the first time and while the execution of the indicated program is ongoing, determining, by the configured computing system, to modify a quantity of the multiple computing nodes in the cluster during the ongoing execution of the indicated program;
identifying, by the configured computing system, a first subset of the multiple computing nodes that each are part of distributed storage at the second time for the ongoing execution of the indicated program, and a second subset of one or more of the multiple computing nodes that are distinct from the multiple computing nodes of the first subset and that are not part of the distributed storage at the second time; and
initiating, by the configured computing system, a change in the quantity of the multiple computing nodes of the cluster while the execution of the indicated program is ongoing in response to the determining to modify the quantity, the initiated change in the quantity being performed for one of the first subset and of the second subset that is selected for the initiated change based at least in part on a type of the determined modifying of the quantity, the initiating of the change being performed by the configured computing system.

12. The non-transitory computer-readable medium of claim 11 wherein the configured computing system is part of a distributed program execution service that provides a plurality of computing nodes configurable to perform distributed execution of programs for clients, wherein the initiating of the execution of the indicated program is performed for a first client and includes attempting to execute one or more jobs of the indicated program on the multiple computing nodes using indicated input data, wherein the multiple computing nodes of the cluster are a subset of the plurality of computing nodes that are provided for use on behalf of the first client, wherein the computing nodes of the first subset that are part of the distributed storage at the second time include a first group of one or more core computing nodes that are each part of a distributed storage system for the first client that stores the indicated input data, wherein the computing nodes of the second subset are a second group of one or more auxiliary computing nodes that are not part of the distributed storage system for the first client, and wherein the initiating of the change in the quantity of the multiple computing nodes includes performing a selection of the one of the first subset and of the second subset for the initiated change based at least in part on whether the initiated change is to remove one or more computing nodes from the cluster or is to add one or more computing nodes to the cluster.

13. The non-transitory computer-readable medium of claim 12 wherein the type of the determined modifying of the quantity of the multiple computing nodes in the cluster is to reduce the quantity of the multiple computing nodes in the cluster by at least one, wherein the performing of the selection of the one of the first subset and of the second subset includes selecting the auxiliary computing nodes of the second subset based on the reducing of the quantity, and wherein the initiating of the change in the quantity includes removing one or more of the auxiliary computing nodes from the cluster.

14. The non-transitory computer-readable medium of claim 11 wherein the type of the determined modifying of the quantity of the multiple computing nodes in the cluster includes one of reducing the quantity of the multiple computing nodes in the cluster and of increasing the quantity of the multiple computing nodes in the cluster, and wherein the initiating of the change in the quantity of the multiple computing nodes includes performing a selection of the first subset for the initiated change and includes modifying a quantity of computing nodes of the first subset.

15. The non-transitory computer-readable medium of claim 11 wherein the computer-readable medium is a memory of the configured computing system that stores the contents, and wherein the contents are instructions that when executed program the computing system to perform the method.

16. A computing system, comprising:
one or more processors; and
one or more modules of a distributed execution service that are configured to, when executed by at least one of the one or more processors, manage distributed execution of programs for clients by, for each of one or more of the clients:
receiving information from the client regarding execution of an indicated program in a distributed manner on a cluster of multiple computing nodes;
initiating the execution of the indicated program in the distributed manner on the cluster of multiple computing nodes at a first time;
at a second time subsequent to the first time and while the execution of the indicated program is ongoing, determining to modify a quantity of first computing nodes in the cluster that are not part of distributed storage for information used for the ongoing execution of the indicated program, the first computing nodes being distinct from at least some computing nodes in the cluster at the second time that each are part of the distributed storage; and
initiating a change in the quantity of the first computing nodes of the cluster while the execution of the indicated program is ongoing and in response to the determining to modify the quantity.

17. The computing system of claim 16 wherein the distributed execution service is a distributed program execution service that provides a plurality of computing nodes configurable to perform distributed execution of programs for the clients of the distributed program execution service, wherein the multiple computing nodes of the cluster for a first of the one or more clients are a subset of the plurality of computing nodes, wherein the at least some computing nodes in the cluster of the first client at the second time that are part of the distributed storage for the first client includes a first group of one or more core computing nodes that are each part of a distributed storage system for the first client, wherein the first computing nodes in the cluster of the first client on which the change in the quantity is initiated are a second group of one or more auxiliary computing nodes that are not part of the distributed storage system and that each executes one or more of a plurality of jobs of the indicated program, and wherein the one or more computing nodes of the cluster for the first client on which one or more jobs are attempted to be executed at the first time include the one or more auxiliary computing nodes.

18. The computing system of claim 17 wherein the information received from the first client is configuration information for the execution of the indicated program for the first client that includes an indication of a quantity of the multiple computing nodes in the cluster for the first client at the first time and that includes one or more criteria that is used in the automatic determining at the second time to modify the quantity of the first computing nodes in the cluster for the first client, and wherein the one or more computing nodes of the cluster for the first client on which one or more jobs are attempted to be executed at the first time further include the one or more core computing nodes.

19. The computing system of claim 16 wherein, for a first of the one or more clients, the cluster for the first client includes one or more of the first computing nodes at the second time, and wherein the automatically initiated change in the quantity of the first computing nodes in the cluster for the first client is to remove at least one of the one or more first computing nodes while the execution of the indicated program for the first client is ongoing on one or more other computing nodes of the cluster for the first client.

20. The computing system of claim 16 wherein, for a first of the one or more clients, the cluster for the first client includes one or more of the first computing nodes at the second time, and wherein the automatically initiated change in the quantity of the first computing nodes in the cluster for the first client is to add at least one additional first computing node while the execution of the indicated program for the first client is ongoing on other of the first computing nodes of the cluster for the first client.

21. The computing system of claim 16 wherein, for a first of the one or more clients, the cluster for the first client includes a quantity of zero of the first computing nodes at the second time, and wherein the automatically initiated change in the quantity of the first computing nodes in the cluster for the first client is to add at least one first computing node while the execution of the indicated program for the first client is ongoing on other computing nodes of the cluster for the first client.

22. The computing system of claim 16 wherein the one or more modules are further configured to, for a first of the one or more clients, automatically initiate a change in quantity of the at least some computing nodes in the cluster of the first client at the second time that each are part of the distributed storage for the first client.

23. The computing system of claim 16 wherein the one or more modules each include software instructions for execution by the computing system.

24. The computing system of claim 16 wherein the one or more modules consist of a means for performing the managing of the distributed execution of the programs for the clients.