nats-server
https://github.com/nats-io/nats-server
Go
High-Performance server for NATS.io, the cloud and edge native messaging system.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
Go not yet supported2 Subscribers
Add a CodeTriage badge to nats-server
Help out
- Issues
- Internal subscription on "$JS.API.CONSUMER.CREATE.mystream" took too long:
- NATS in the cluster deletes messages in the 'nak timeout' state when updating the stream.
- Memory leak of nats cluster
- Duplicate Connections + Authorization Failures After Resetting Cluster Connections Leading to Lost Messages Across the Cluster [v2.10.14]
- [Draft] Parametrize 2 Js/Fs benchmarks
- The consumer connects to NATS but fails to consume data.
- Streams getting marked as orphaned and deleted when transitioning from one non-clustered server to a cluster
- Healthcheck fails when JetStream account is removed from configuration
- Too many CPU/System resource used after many consumer created in idle cluster
- WorkQueue jetstream messages are not deleted on non-leader nodes when used as mirror source [v2.10.14]
- Docs
- Go not yet supported