1a6c5f1c90
- Send snapshot only if leader - When processing snapshot, start with a smaller inactivity interval that will double up to 10sec or use 10sec directly once we get a message. Reason for that is that it is possible that the request for snapshot is sent while the leader has not yet setup the subscription that receives the requests (or subscription has not fully reached the cluster). - Don't remember snapfile on err. - Do not consider current if we have not had any activity. - Stabilize stream scale up under active heavy publishing. - Due to the publish pressure move the check for followers direct subs spinning up til after we stop publishing. Signed-off-by: Derek Collison <derek@nats.io> Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
NATS is a simple, secure and performant communications system for digital systems, services and devices. NATS is part of the Cloud Native Computing Foundation (CNCF). NATS has over 40 client language implementations, and its server can run on-premise, in the cloud, at the edge, and even on a Raspberry Pi. NATS can secure and simplify design and operation of modern distributed systems.
Documentation
- Official documentation
- FAQ
- Watch a video overview of NATS to learn more about its origin story and design philosophy.
Contact
- Twitter: Follow us on Twitter!
- Google Groups: Where you can ask questions
- Slack: Click here to join. You can ask question to our maintainers and to the rich and active community.
Contributing
If you are interested in contributing to NATS, read about our...
Roadmap
The NATS product roadmap can be found here.
Security
Security Audit
A third party security audit was performed by Cure53, you can see the full report here.
Reporting Security Vulnerabilities
If you've found a vulnerability or a potential vulnerability in the NATS server, please let us know at nats-security.
License
Unless otherwise noted, the NATS source files are distributed under the Apache Version 2.0 license found in the LICENSE file.