Skip to content

Insufficient Resources

A message similar to one of the following appears in an order run log to alert you:

Order run terminated - either RAM or disk exceeded the limit.

Container terminated. RAM/Disk usage exceeded the limit.

Error getting pod working dir ... Insufficient memory for running the container.

Not enough allocatable resources.

Visual example in Automation

(Screenshot of error log)

Details

Recipes contain at least one configured resource allocation, or runtime setting, to allocate memory and ist space on the agent for each order run that's processed.

The default memory runtime setting allocates 1024 MB of memory for each order run; the default disk space runtime setting allocates 2048 MB of disk space for each order run.

These are generally sufficient to run most orders, however, some order runs are resource-intensive.

Potential causes

Certain order runs can be more resource-intensive than others. For example, those with large queries, heavy use of variables, or data sources and sinks.

Solution

Step1: Verify the error

  1. Navigate to the Order Run Details page for the affected order run.
    • To view log entries for the entire order run, click Order Run Logs.
    • To view the order run logs per node, select a failed node to open Node Details, then select View Node Logs under Logs.
  2. Filter for the error.
    • Under Resources, select RAM and/or Disk.
    • Search for "order run terminated," "container terminated," or "insufficient memory."
  3. Based on the error message, make adjustments to your container or recipe setup.

Step 2: Adjust the setup

Resources for all order runs:

  1. From the Recipes page, select the impacted recipe from the list.
  2. Select the Schedules tab.
  3. Add or edit a schedule.
  4. Specify resource values in the dialog.
  5. Save your changes and rerun the order.

Resources for container node executions:

  1. Open the Node Editor of the affected container node.
  2. Select the Configuration tab
  3. Select Container Settings.
  4. Assign max RAM and/or disk space.
  5. Save your changes and rerun.

Tip

Use an empty schedule to set run once resources. When you apply a schedule to a variation and activate that scheduled order, the system will allocate resources—up to the maximum 1024 MB of RAM and 2048 MB of disk space—to every order run done for that schedule. To set resource maximums for run-once orders, create a schedule without a frequency and only enter values for RAM and disk space.

Order Run Logs

Runtime Resources

Schedule Settings

Configure Container Nodes

Automation Agents

Note

Still not working? Contact DataKitchen Support. We can work through this together.