JetStream: panic: runtime error: makeslice: cap out of range about nats-server HOT 6 CLOSED

I would be interested in knowing about the OOMs also. Be good to get a memory profile from the server before it gets OOM'd.

from nats-server.

Would it be possible to have a call with the Synadia Team?

If you create a backup of the stream and try to restore it somewhere else does the issue re-occur? If so would it be possible to get access to the backup?

from nats-server.

Keeping open so that we can figure out how the system got into that state possibly.

from nats-server.

Hey @derekcollison, thanks for the quick turnaround on this! Would be more than happy to hop on a call if it'd be helpful. I'd also be interested in discussing the occasional OOM issues we encounter and how we can troubleshoot and/or provide actionable info here.

In the meantime, I'll attempt a backup/restore to see if I can reliably reproduce the issue. If so, happy to share for troubleshooting purposes.

from nats-server.

It remind me old problems, in 2.9.3
#3517
I past there was problem with slow disks. We used GP2 drives, and at that time I was told that for proper work I need NVMe disk.
I'm our case data were ending in $G stream. And sync with actual stream caused out of memory events.
We stopped using jetstream to avoid issue.

from nats-server.

The product has advanced quite a bit since 2.9.3, with 2.9 series at 2.9.25 and the current version 2.10 at 2.10.12..

from nats-server.