The official patch release of EventStoreDB OSS & Commercial version 22.10.2 LTS is now available.
This is a patch to the 22.10 LTS release, which will be supported until October 2024. Read more about our versioning strategy.
The complete changelog can be found here. If you need help planning your upgrade or want to discuss support, please contact us.
EventStoreDB 22.10.2 is available for the following operating systems:
Additionally, you can find docker images including the preview ARM64 image on Dockerhub.
22.10.2 will be supported for 2 years until version 24.10.0 is released in October 2024.
If you are already running 22.10.0, then we recommend that you upgrade to 22.10.2, especially if you have experienced either of the errors fixed in this patch. These are detailed below.
If you are on 21.10.x and wondering if you should upgrade, then check the feature highlights to see what’s new in 22.10.2 vs 21.10.0. If you are not wanting to upgrade for any of those features, then ensure that you are on the latest version of 21.10 to get the latest fixes and patches.
To upgrade a cluster from 21.10.x or 22.10.x, a usual rolling upgrade can be done:
Downloads are available on our website.
The packages can also be installed using the following instructions.
curl -s https://packagecloud.io/install/repositories/EventStore/EventStore-OSS/script.deb.sh | sudo bash
sudo apt-get install eventstore-oss=22.10.2
curl -s https://packagecloud.io/install/repositories/EventStore/EventStore-OSS/script.deb.sh | sudo bash
sudo apt-get install eventstore-oss=22.10.2~preview1
choco install eventstore-oss -version 22.10.2
docker pull eventstore/eventstore:22.10.2-focal
docker pull eventstore/eventstore:22.10.2-bullseye-slim
It was possible for scavenging on EventStore 22.10.0 and 22.10.1 to fail with the error message “Could not get TimeStamp range for chunk” if a scavenge had previously been run on an older version of EventStore. This happened when the previous scavenge had scavenged away all of the events in a chunk (leaving it empty) but hadn’t scavenged the index.
This case is now correctly handled in 22.10.2
Previously, the gRPC client was not getting notified when the creation or deleting of a persistent subscription failed, resulting in these failed requests just timing out.
This version will now correctly report the fact that the request failed back to the client.
For more detailed information about these fixes and others in this release, please check the Changelog.
Read EventStoredDB documentation here.
Previous release notes can be found here.
If you encounter any issues, please don’t hesitate to open an issue on GitHub if there isn’t one already.
Additionally, there is a fairly active discuss channel, and an #eventstore channel on the DDD-CQRS-ES community
If you have any questions that aren't covered in these release notes or the docs, please feel free to reach out.