Before you begin
About this task
- Open the Processing page then click the Engines tab.
Click the name of cluster to which you want to add Remote
If this cluster already contains some engines, details about the engine availability is displayed on this list as well as on the Cluster details blade.
icon on the Engines tab.
Select the Remote Engines to include in the cluster.
You can only select Remote Engines from the same environment where your cluster is.
You can select Remote Engines from any workspace on that environment. However, if the workspaces are different, the selected Remote Engines will be placed into the cluster's workspace.Note: When deploying Routes and data services on a cluster, all Remote Engines assigned to it must be of the same version (v2.8.4 or above).
If Job tasks are already running or scheduled on the Remote
Engine you selected, choose your preferred option to update the cluster's run
You can reschedule the tasks running on the engine to run on the cluster:
- Without a run profile
- By duplicating the engine run profiles and associating them with the cluster
- Using the cluster run profile
The number of engines belonging to a cluster appears in brackets next to its name on the Engines tab of the Processing page.
When choosing to run a Job task on the cluster, it is executed in a round-robin manner on the engines belonging to the cluster. The task is executed on the first available Remote Engine, then the next and so on, while putting the ones the task was executed on to the end of the list. If a Remote Engine is not available, the task is executed on the next available engine.
|The tasks are deployed simultaneously to all the Remote Engines of the cluster. Before deploying a new version of a task, you will need to undeploy the currently running version, which will result in service interruption.
|If the Remote Engine cluster contains more than one Remote Engine, the tasks are deployed one by one to the Remote Engines of the cluster. This means that for a short time, different Remote Engines will be running different versions of the task, therefore you can avoid service interruption.