ExecutionRoutes
Related Docs:
object ExecutionRoutes
| package rest
the config from which worker routes will be built
the echange from which values will be requested should a request arrive with MatchDetails headers
the request handler for running and cancelling jobs
the echange from which values will be requested should a request arrive with MatchDetails headers
the config from which worker routes will be built
the request handler for running and cancelling jobs
(Since version ) see corresponding Javadoc for more information.
The execution routes can execute commands on the machine, as well as upload files to workspaces.
Use Case Example w/ Spark
Consider an Apache Spark use-case, where we have a command we want to execute on a machine which depends on data being uploaded from some worker nodes.
One approach would be to execute an initial command in order to 'select' a number of workers. That could be a command to actually get data, or just choose which workers match particular criteria.
Once we have chosen that/those worker(s), we have each Spark node make a request to upload its partitioned data to them in a prepare step asynchronously (fire and forget).
The workers could then perform actions based on normal executions via the exchange which specify selection criteria that target those specific nodes (as we want to ensure our commands operate on the same files which were uploaded by specifying UploadDependencies.
Combines both the worker routes and some job output ones.
NOTE: These routes are separate from the WorkerRoutes which handle jobs that have been redirected from the exchange
the config from which worker routes will be built
the echange from which values will be requested should a request arrive with MatchDetails headers
the request handler for running and cancelling jobs