Zeebe log stream FULL Error

Camunda 8 Topics
1

Hi Guys

We are seeing intermittent issue in zeebe logs stating log steam error FULL at 00 th Hour when burst of order is coming in order management and due to that our order got stuck during fulfillment.

Sample log:

2026-07-30 16:01:08.475 [Broker-6] [zb-fs-workers-2] [SnapshotStore-14] DEBUG
io.camunda.zeebe.logstreams.snapshot - Taking temporary snapshot into /usr/local/zeebe/data/raft-partition/partitions/14/snapshots/1749360305-7-5094834351-5094753717.
2026-07-30 16:01:08.790 [Broker-6] [zb-fs-workers-3] [SnapshotStore-14] INFO
io.camunda.zeebe.snapshots.impl.FileBasedSnapshotStore - Committed new snapshot 1749360305-7-5094834351-5094753717
2026-07-30 16:01:08.791 [Broker-6] [zb-fs-workers-3] [SnapshotStore-14] DEBUG
io.camunda.zeebe.snapshots.impl.FileBasedSnapshotStore - Deleting previous snapshot 1749154351-7-5094031174-5094003091
2026-07-30 16:01:08.797 [Broker-6] [raft-server-6-14] [raft-server-14] DEBUG
io.camunda.zeebe.journal.file.SegmentsManager - raft-partition-partition-14 - Deleting log up from 1749087458 up to 1749291680 (removing 3 segments)
2026-07-30 16:01:23.707 [Broker-6] [zb-actors-2] [InterPartitionCommandReceiverActor-6] WARN
io.camunda.zeebe.broker.transport - Failed to write command PROCESS_MESSAGE_SUBSCRIPTION DELETE from 2 to logstream (error = FULL)
2026-07-30 16:01:23.707 [Broker-6] [zb-actors-2] [InterPartitionCommandReceiverActor-6] WARN
io.camunda.zeebe.broker.transport - Failed to write command PROCESS_MESSAGE_SUBSCRIPTION CREATE from 2 to logstream (error = FULL)
2026-07-30 16:01:23.805 [Broker-6] [zb-actors-1] [InterPartitionCommandReceiverActor-6] WARN
io.camunda.zeebe.broker.transport - Failed to write command PROCESS_MESSAGE_SUBSCRIPTION DELETE from 4 to logstream (error = FULL)
2026-07-30 16:01:23.805 [Broker-6] [zb-actors-1] [InterPartitionCommandReceiverActor-6] WARN
io.camunda.zeebe.broker.transport - Failed to write command PROCESS_MESSAGE_SUBSCRIPTION CREATE from 4 to logstream (error = FULL)

We are unable to get any solution to fix this issue in production, Can someone pls suggest something to fix it?

also we tried to change some config like zeebe: broker: data: logSegmentSize: 1024MB processing: maxCommandsInBatch: 100 backpressure: algorithm: vegas enabled: true After applying of these config we got stuck in more problem since our 8k orders got stuck

2

This “error = FULL” is a logstream backpressure/hot-partition issue related to burst load, correlation key distribution, or exporter lag rather than disk space. I found the following relevant resources:

Does this help? If not, can anyone from the community jump in? :waving_hand:

:light_bulb: Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. :robot: