This error usually indicates that the process was killed by the operating system due to running out of memory (OOM).

Solutions

Possible solutions include increasing the amount of memory available to the run, reducing the amount of memory used by the ops in the run, or configuring the executor to run fewer ops concurrently.

To investigate:

• Check the ECS console, if you are using the AWS agent

• There is a beta feature in Dagster that can capture additional CPU and memory metrics. To use it, launch a run with the tag dagster/run_metrics: true . To add this tag:

  • Select the asset you want to materialize

  • Shift+click the "Materialize" button to open the Launchpad

  • Click Edit tags and enter dagster/run_metrics as the key and true as the value.

• To resolve this by increasing resource limits, you can modify the dagster_cloud.yaml file in your Git repo to increase these limits. For more information, see the ECS agent configuration reference.