Eventing backend stopped receiving events due to full storage
NATS JetStream backend stopped receiving events due to full storage.
You observe the following behavior in the Event Publisher Proxy (EPP):
507 Insufficient StorageHTTP Status from EPP on the publish request.
cannot send to stream: nats: maximum bytes exceededin the EPP logs.
In Kyma, the default retention policy for NATS JetStream is Interest. This retention policy keeps messages in the stream if they can't be delivered to the sink, as long as there are consumers in the stream that match the published event's subject.
If there are too many undelivered events, the NATS JetStream storage may get full. To prevent event loss, the backend stops receiving events, and no further events can be persisted to the stream.
NOTE: If you delete a Subscriber (sink) while there is still a Kyma Subscription pointing to that sink, the events published to that Subscription pile up in the stream and possibly delay the event delivery to other Subscribers.
There are several ways to free the space on NATS JetStream backend:
- If the published events are too large, the consumer cannot deliver them fast enough before the storage is full. In that case, either slow down the events' publish rate until the events are delivered, or scale the NATS backend with additional replicas.
Interestretention policy specifies that events published to the subject are not kept in the stream if they don't match any consumer filter. You can delete a Kyma Subscription, which automatically removes all the pending messages in the stream that were published to that Subscription's subject.
- In case the events' publish rate is very high (more than 1.5k events per second), speed up the event dispatching by increasing the
maxInFlightMessagesconfiguration of the Subscription (default is set to 10) accordingly. Due to low
maxInFlightMessages, the dispatcher will not be able to keep up with the publisher, and as a result, the stream size will keep growing.