One of the nodes in our 3 node k8s cluster wouldn't start, and output the following panic stack trace.
The only way we could restore it was to re-deploy NATS and drop the persistent volumes.
Hopefully the stack trace gives some clue.
Prior to this I had attempted to delete the streams and consumers using NATS CLI
NATS Server Version: 2.5.0
Deployment method: Kubernetes Helm Chart Version 0.8.9
Hi @andreib1, thanks for the report. This should have been solved in the NATS Server v2.6.0 release via #2545 along other restart improvements so recommend to upgrade.
One of the nodes in our 3 node k8s cluster wouldn't start, and output the following panic stack trace. The only way we could restore it was to re-deploy NATS and drop the persistent volumes. Hopefully the stack trace gives some clue. Prior to this I had attempted to delete the streams and consumers using NATS CLI
NATS Server Version: 2.5.0 Deployment method: Kubernetes Helm Chart Version 0.8.9