Restart a Maia runner🔗

Runner type:

Maia Hybrid

Runner platform:

AWS ✅ Azure ✅ Snowflake ✅ Matillion ✅

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

Maia runners can sometimes crash or become unstable.
You changed the Maia runner'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 Maia runner updates.

Prerequisites🔗

To restart a Maia runner from the Agents screen in Maia, you must have the Manage runners service enabled for your user account.

Note

There is no granular "restart agent only" permission. Users who need to restart Maia runners must have full Manage runners access. Alternatively, users with appropriate permissions in your Maia runner provider (AWS, Azure, or Snowflake) can restart Maia runners directly from the Maia runner provider console without requiring Manage runners access in Maia.

How to restart your Maia runner🔗

You can restart your Maia runner in one of two ways:

From the Runners screen in Maia.
From the cloud provider's control panel:
- AWS
- Azure
- Snowflake
Note

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

Read Pause a Maia runner for an alternative way of managing Maia runners that need restarting.

Restart from the Runners screen🔗

In the left navigation, click the Runners & Instances icon . Then, select Runners from the menu.
Locate the Maia runner you want to restart and click the three dots ....
Click Restart runner.
Click Yes restart to confirm.

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

The Restart runner option sends a graceful shutdown request to all the instances (tasks/pods) contained within the Maia runner 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 Maia runner service will then start up new, replacement instances.

Running pipelines will continue as normal. Any pipeline tasks that are sent to a Maia runner 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 a Maia runner 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 Maia runner instances will take on any new pipeline tasks.

Restart an AWS ECS Fargate Maia runner🔗

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

To restart your AWS Maia runner, 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 Maia runner, and click Update service.
Select the latest task definition and click Update.

Restart an Azure Maia runner🔗

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

There are two ways you can restart an Azure Maia runner:

The Azure Portal
The Azure CLI

Using the Azure Portal🔗

To restart your Maia runner 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 Maia runner, 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 a Maia runner 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"

Restart a Maia runner for Snowflake🔗

You can restart the Maia runner by suspending and resuming the compute pool from within Snowflake. Suspending the compute pool will prevent the Maia runner from being used by Maia, and will stop all running tasks. Resuming the compute pool will make the Maia runner available for use again.

From your Snowflake Home screen, click Data Products → Apps. You must be using the role that originally installed the application.
Locate Matillion Maia in the list of apps, and click to select it. If you have multiple installs of the Native App, select the one you wish to restart.
Click the Control Panel tab.
Click Suspend Compute Pool, then click Suspend to confirm. This will put the pool into a Stopping state and change the Maia runner status to Suspending.

Warning

This will suspend the compute pool and all Maia runner instances that it supports. This will stay suspended until you actively click Resume Compute Pool.
Wait for the Maia runner to stop. This may take a few minutes.
When the Maia runner is in a Suspended state, click Resume Compute Pool. This will put the pool into a Starting state and change the Maia runner status to Pending.
Wait for the Maia runner to start. This may take a few minutes.

Note

After the compute pool changes to an Active state, the Maia runner status may remain as Pending for a few minutes before changing to Running.