optimiseTables, because the backup and the optimise task can’t run at the same time there.
Which hosts are short of memory
ECS registers a little less memory than an instance type’s nominal size. The server’s memory limit allows for neither that gap nor the backup and optimise tasks, which need 256 MiB each. These figures were measured on 18 November 2026 with fjall 40.0.1 on arm64 hosts.m7g.xlarge is the enterprise tier’s default, m7g.large the resilient tier’s and t4g.medium the standard tier’s. Hosts with 32 GiB of memory have room for both tasks.
With optimiseTables set on a 4 GiB or 8 GiB host, a backup or optimise run that starts while the other is running can’t start.
Nothing alarms when a run can’t start
When ECS can’t place the task, EventBridge still counts the scheduled run as delivered. The schedule’s failed invocation alarm stays quiet, and nothing reaches its dead letter queue. The task never starts, so it writes no log line, and the backup status alarms have nothing to read. Fjall measured this on fjall 40.0.1 on 18 November 2026. In fjall 40.0.1 the backup heartbeat alarm waits for a first successful backup before it pages, so a database that has never had room for a backup never pages. A database deployed without an alarm topic has no ClickHouse alarms at all.Check whether your database is affected
Run these from your Fjall project, with the target that holds the database.-
Find the ClickHouse host and its instance type.
-
Read how much memory ECS has left on the host. The ClickHouse cluster is named
Compute. Read it outside the backup window, because a running backup or optimise task holds its 256 MiB.
optimiseTables means the backup and the optimise task can’t run at the same time.
Keep a copy of the data until a fixed release ships
No setting in a released version lets the backup fit on a 16 GiB host. These steps keep a copy of the data until one does.-
Find the ClickHouse data volume. It’s the volume whose owner ends in
PersistentDataVolumeunder your database’s name.If that lists nothing, list the volumes attached to the host from the first check. The data volume is the one that isn’t the root volume. -
See whether AWS Backup already covers it. Recent recovery points mean the volume is already in a backup plan.
-
If it isn’t covered, take a snapshot of the volume each day until you’ve upgraded.