Problem:
Batch Analysis jobs fail with the following error:
MinIO storage is too low (X %) in order to start batch analysis
Cause:
In order avoid storage saturation events, SImA prevents Batch Analysis jobs if the available disk space is less than 10%, as defined by the MINIO_LOW_STORAGE_LIMIT in the default.env file found in the SImA installation directory.
MINIO_LOW_STORAGE_LIMIT=0.01
The following locations are bound by the MinIO low storage limit:
-
/var/lib/docker/volumes(the default location for Docker defined volumes). - Any custom mount point, as defined by either the
MINIO_VOLUME_PATH(SImA version 1.3 or lower) orMINIO_VOLUME_PATH_NEW_FS(SImA version 1.4) variables in the.env(hidden) file located in the SImA installation directory.
Solution:
The recommendation would be to increase the disk allocation of the affected filesystem, or remove unnecessary files to free space.
Alternatively, the MINIO_LOW_STORAGE_LIMIT can be lowered by adding a line to the custom.env file found in the SImA installation directory.
MINIO_LOW_STORAGE_LIMIT=0.01
In this example the low storage limit is set to 1%, where Batch Analysis jobs would be prevented if the available storage is less than this value.
The SImA stack must be redeployed for this change to take effect: Signals Image Artist: How do I redeploy/restart the container stack?
See also: Signals Image Artist: "Not enough MinIO storage left" message during Upload or Harmony Transfer