Fix clw-scheduler-oom: OpenClaw scheduler out of memory during task scheduling

Fri, 17 Apr 2026 02:24:49 +0800

Fix clw-scheduler-oom: OpenClaw scheduler out of memory during task scheduling

1. Symptoms

The clw-scheduler-oom error manifests when OpenClaw’s central scheduler component fails to allocate memory for incoming tasks. This typically halts task dispatching across the cluster, leading to cascading failures in distributed workloads.

Common symptoms include:


[2024-10-18 14:32:15] ERROR clw-scheduler: clw-scheduler-oom: Heap exhausted (requested 4KiB for task slot, available 0B). Total heap: 2GiB/2GiB used.
[2024-10-18 14:32:15] WARN clw-scheduler: Dropping 127 pending tasks due to OOM. Task IDs: [task-abc123, task-def456, ...]
[2024-10-18 14:32:16] FATAL clw-coordinator: Scheduler unresponsive. Cluster health: DEGRADED.

Scheduler logs flood with OOM events.
clw status reports scheduler_heap_usage: 100%.
Worker nodes idle despite pending jobs in the queue.
Metrics endpoint (/metrics) shows clw_scheduler_tasks_pending > 10000 and clw_scheduler_memory_rss > limit.
Cluster-wide latency spikes as tasks backlog.

In Kubernetes deployments, pods may enter OOMKilled state if scheduler shares node resources:

Task-Allocation on ErrorVault — Developer Error Code Dictionary

Fix clw-scheduler-oom: OpenClaw scheduler out of memory during task scheduling

Fix clw-scheduler-oom: OpenClaw scheduler out of memory during task scheduling

1. Symptoms