We are pleased to announce the official release of EventStoreDB OSS & Commercial version 21.10.7 long-term support (LTS).
This LTS release will be supported until October 2023. Read more about our versioning strategy here. The complete changelog can be found here. If you need help planning your upgrade or want to discuss support, please contact us here.
EventStoreDB 21.10.7 is available for the following operating systems:
- Ubuntu 18.04
- Ubuntu 20.04
- CentOS 7 (Commercial version)
- Amazon Linux 2 (Commercial version)
- Oracle Linux 7 (Commercial version)
Additionally, an experimental build for ARM64 processors will be available shortly as a Docker image.
Ubuntu 16.04 is not supported anymore as of 21.10.0 release, more information about Ubuntu’s release and support policy can be found here.
Where Can I Get the Packages?
Downloads are available on our website.
The packages can also be installed using the following instructions.
Ubuntu 18.04/20.04 (via packagecloud)
curl -s https://packagecloud.io/install/repositories/EventStore/EventStore-OSS/script.deb.sh | sudo bash sudo apt-get install eventstore-oss=21.10.7
Windows (via Chocolatey)
choco install eventstore-oss -version 21.10.7
Docker (via docker hub)
docker pull eventstore/eventstore:21.10.7-focal
docker pull eventstore/eventstore:21.10.7-buster-slim
Prevent gRPC subscriptions from hanging while catching up (EventStore#3532)
If the server was under extremely heavy load, such that read requests were queued for more than 10 seconds before being processed, then it was possible for gRPC subscriptions to $all and to streams to stall while catching up. A stalled subscription would not be terminated on the client side, nor receive further events. This has been fixed so that the subscriptions will continue to receive events.
To upgrade a cluster from 20.10.x or 21.10.x, a usual rolling upgrade can be done:
- Pick a node (start with follower nodes first, then choose the leader last).
- Stop the node, upgrade it and start it.
There is no way to perform a rolling upgrade between version 5.x and version 21.10.x due to changes in the replication protocols and the way nodes gossip and host elections.
As such, the upgrade process from 5.x is as follows:
- Take down the cluster.
- Perform an in-place upgrade of the nodes, ensuring that the relevant configuration and certificates are set up.
- Bring the nodes back online and wait for them to stabilize.
Documentation and previous releases notes
If you encounter any issues, please don’t hesitate to open an issue on GitHub if there isn’t one already.
If you have any questions that aren't covered in these release notes or the docs, please feel free to reach out.