Restart an agent

You might need to restart your agent from time to time for any of the following reasons:

Agents can sometimes crash or become unstable.
You changed the agent's configuration.
You added a new certificate to be used for setting up a proxy server.
You added new Python libraries.
You added new third-party drivers.
To receive agent updates.

You can restart the agent in one of two ways:

From the Agents screen in the Data Productivity Cloud.
From the cloud provider's control panel:
- AWS
- Azure
Note

A changed agent deployment configuration may require a restart of the cloud provider service to take effect.

Read Pause an agent for an alternative way of managing agents that need restarting.

Restart from the Agents screen

On the Agents screen, locate the agent you want to restart and click ....
Click Restart agent.
Click Yes restart to confirm.

This feature takes advantage of how a cloud provider will manage an installed agent service by ensuring that the required amount of agent instances (tasks/pods, depending on your deployment) are always started if any drop.

The Restart agent option sends a graceful shutdown request to all the instances (tasks/pods) contained within the agent service on the cloud provider. Each instance will complete any pipeline tasks currently in progress, or wait for any open transactions to complete, and then shut itself down. The agent service will then start up new, replacement instances.

Running pipelines will continue as normal. Any pipeline tasks that are sent to an agent that's currently restarting will be queued until the new service is back up and running. Your pipelines will be unaffected, though they may take a few minutes longer than normally expected for execution to complete.

Assuming that there are no running tasks, it usually takes a few minutes for an agent instance to shutdown and a new instance to start back up. If you have multiple instances and one is working on a longer pipeline task or currently has an open transaction, then the other restarted agent instances will take on any new pipeline tasks.

Restart an AWS ECS Fargate agent

You will need access to your AWS account with the appropriate permissions.

To restart your AWS agent, follow these steps:

Log in to the AWS console.
In the AWS console, type Elastic Container Service in the search bar, and select that service.
Locate the ECS service running your agent, and click Update service.
Select the latest task definition and click Update.

Restart an Azure agent

You will need access to your Azure account with the appropriate permissions.

There are two ways you can restart an Azure agent:

The Azure Portal
The Azure CLI

Using the Azure Portal

To restart your agent using the Azure Portal, follow these steps:

Log in to the Azure Portal.
In the search bar at the top of the Azure Portal, enter "Container apps", and click the Container Apps link in the results menu.
Click your chosen container app from the list.
Click Application to display a context menu.
Click Revisions and replicas.
Click on the name of the intended Active Revision.
A panel to the right will appear. At the top of Revision details, click Restart.

Using the Azure CLI

To restart your agent, you can open the Azure CLI either locally on your machine, or through the Azure portal.

Use the following command:

az containerapp revision restart --revision <REVISION_NAME> --resource-group <RESOURCE_GROUP_NAME> --subscription <SUBSCRIPTION_NAME>"

For example, if you have an agent called cloud-agent-dev in a resource group called cloud-agent-dev, and your Azure subscription is called Matillion Dev, you are required to use the following command:

az containerapp revision restart --revision cloud-agent-dev --resource-group cloud-agent-dev --subscription "Matillion Dev"