Task details
The Task details part of the task details page shows the following information.
Engine
Shows the selected Talend Remote Engine and its status and availability.
Clicking on the info icon shows you the Metric path that is used at deployment time to retrieve metric data, for example, the number of requests at runtime. The default value is the data service or Route name, and we recommend to keep this value to see the metric data displayed on the Task Details page. If this field is empty, no metric information will be displayed on the page.
If the task is running, the tooltip for the info icon will also show the HTTP port on which the task runs and which can be used by the Operator to set up other services, for example, the AWS ELB or an API Gateway. For Talend Runtime-based deployments, the default port is 8040.
Artifact
Shows the name of the Route or data service used in the task and its version. If there is a more recent artifact version available than the one used in the task, a notification is displayed next to the version number. Depending on your deployment strategy, you need to undeploy the task before you update the artifact version.
Deployment strategy
-
Single node
Applies to deployments on a single Remote Engine that is not part of a Remote Engine cluster. This is the standard deployment strategy that requires you to undeploy a task before you can deploy a new version.
-
Parallel
Applies to Remote Engine clusters. The Deploy action will deploy the tasks 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.
When a task is deployed on the cluster for the first time, the deployment strategy always automatically switches to this Parallel strategy, regardless of your chosen strategy.
-
Rolling
Applies to Remote Engine clusters. If the Remote Engine cluster contains more than one Remote Engine, the Deploy action will deploy the tasks 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.