Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maia.ai/llms.txt

Use this file to discover all available pages before exploring further.

You might need to restart your from time to time for any of the following reasons:
  • s can sometimes crash or become unstable.
  • You changed the ‘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 updates.

​
Prerequisites

To restart a from the Runners list in , you must have the Manage runners service enabled for your user account.
There is no granular “restart only” permission. Users who need to restart s must have full Manage runners access. Alternatively, users with appropriate permissions in your provider (AWS, Azure, or Snowflake) can restart s directly from the provider console without requiring Manage runners access in .

​
How to restart your Maia runner

You can restart your in one of two ways:
  • From the s screen in .
  • From the cloud provider’s control panel:
    A changed deployment configuration may require a restart of the cloud provider service to take effect.
Read Pause a for an alternative way of managing s that need restarting.

​
Restart from the Maia runner screen

  1. In the left navigation, click s. Then, select Runners from the menu.
  2. Locate the you want to restart and click the three dots ….
  3. Click Restart runner.
  4. Click Yes restart to confirm.
This feature takes advantage of how a cloud provider will manage an installed service by ensuring that the required amount of 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 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 service will then start up new, replacement instances. Running pipelines will continue as normal. Any pipeline tasks that are sent to a 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 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 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 , follow these steps:
  1. Log in to the AWS console.
  2. In the AWS console, type Elastic Container Service in the search bar, and select that service.
  3. Locate the ECS service running your , and click Update service.
  4. 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 :
  • The Azure Portal
  • The Azure CLI

​
Using the Azure Portal

To restart your using the Azure Portal, follow these steps:
  1. Log in to the Azure Portal.
  2. In the search bar at the top of the Azure Portal, enter “Container apps”, and click the Container Apps link in the results menu.
  3. Click your chosen container app from the list.
  4. Click Application to display a context menu.
  5. Click Revisions and replicas.
  6. Click on the name of the intended Active Revision.
  7. A panel to the right will appear. At the top of Revision details, click Restart.

​
Using the Azure CLI

To restart your , 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 called cloud-runner-dev in a resource group called cloud-runner-dev, and your Azure subscription is called Matillion Dev, you are required to use the following command: 
az containerapp revision restart --revision cloud-runner-dev --resource-group cloud-runner-dev --subscription "Matillion Dev"

​
Restart a Snowflake Maia runner

You can restart the by suspending and resuming the compute pool from within Snowflake. Suspending the compute pool will prevent the from being used by , and will stop all running tasks. Resuming the compute pool will make the available for use again.
  1. From your Snowflake Home screen, click Data Products → Apps. You must be using the role that originally installed the application.
  2. Locate Matillion 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.
  3. Click the Control Panel tab.
  4. Click Suspend Compute Pool, then click Suspend to confirm. This will put the pool into a Stopping state and change the status to Suspending.
    This will suspend the compute pool and all instances that it supports. This will stay suspended until you actively click Resume Compute Pool.
  5. Wait for the to stop. This may take a few minutes.
  6. When the is in a Suspended state, click Resume Compute Pool. This will put the pool into a Starting state and change the status to Pending.
  7. Wait for the to start. This may take a few minutes.
    After the compute pool changes to an Active state, the status may remain as Pending for a few minutes before changing to Running.