Skip to main content
Applies to: All Domino versions. Disk size configuration in project settings is available from Domino v4.4 and later. The default disk size is 10 GB for versions before v4.4 and 15 GB for v4.4 and later.

​
Issue

An execution fails with the following error in the logs:
The execution has exceeded the available disk space on the compute instance.

​
Root Cause

Each execution runs inside a compute instance with a finite amount of disk space. Total disk usage combines project files, external Git repository contents, the compute environment image, and any data generated during the run. When combined usage exceeds the available disk size, the execution fails. Crash or dump files left behind by integrated development environments (IDEs) or libraries can also consume large amounts of disk space without being immediately visible.

​
Resolution

​
For users

  1. Switch to a different hardware tier. This moves the execution to a different compute instance with available disk space. It’s the quickest fix if you don’t have admin privileges.
  2. Reduce project data. Remove unnecessary files from the project. Git repository contents count toward disk usage.
  3. Move large files to Datasets. Move large project files to a Domino Dataset rather than keeping them in the project directory.
  4. Check for crash or dump files. Jupyter and other IDEs can crash and leave large files in the workspace that aren’t immediately visible.
  5. Increase the disk size (v4.4 and later). In your project, go to Settings → Hardware & Environment → Workspace and Jobs Volume Size and increase the allocated disk size. Changes apply to new workspaces only and don’t affect currently running sessions.

​
For admins

  1. Place the affected executor into Maintenance Mode to take it out of service.
  2. In the Domino Dispatcher UI, locate the executor and verify that no executions are currently running on it. Then terminate the executor to release the storage. Because executors are ephemeral, terminating one is a safe and fast resolution.
Note: Garbage collection may also recover disk space on the executor without requiring termination, but termination is the fastest option. If this issue recurs, consider increasing the default disk size using the Central Config setting: com.cerebro.domino.computegrid.kubernetes.volume.volumesSizeInGB

​
Additional information

Domino v4.0 and later: Each execution gets its own dedicated volume and is no longer affected by shared resource contention from other executions. Users on v4.4 and later can adjust their individual disk size in project settings. Executor maintenance mode: Domino polls executors for disk status and automatically places them into Maintenance Mode when a partition has less than 10% free space. A common scenario is that the disk sits just above this threshold and an execution fills the remaining space. When this happens, new executions on that executor can fail repeatedly until an admin intervenes. Domino v3.6 and earlier: On startup, Domino copies the project files and the compute environment Docker image to a partition on the executor. If this data exceeds the available disk space, the execution fails on startup. Long-lived executors can also accumulate cached project data and environment images over time, gradually filling the disk.
Last modified on October 12, 2026