Hi, there is a self-hosted WeaviateDB (v1.19.0) running by docker compose in my project. Is it possible to upgrate the DB to the latest version (v1.27.x)? If yes, what is the steps to upgrate or migrate ? And is there any risk?
Good morning @AU_Jay,
Welcome to our community! It’s lovely to have you here.
That’s an absolutely great question. Generally, we recommend upgrading one major release at a time as there are new implementations and significant changes that can be crucial. After each upgrade, allow Weaviate to restart and load, then run a node-status check to ensure everything is healthy before proceeding to the next major release. For example:
• 1.20 > 1.21 > 1.22, and so on.
If there’s no higher risk on your end and you have backups, I would suggest using the latest stable release in each major version as follows:
• 1.19 > 1.23.16
• 1.23.16 > 1.24.25
• 1.24.25 > 1.25.21 (RAFT Schema Implementation)
• 1.25.21 > 1.26.7
• 1.26.7 > 1.27.3
I’ve tested locally upgrading from 1.23.16 to 1.25.21 and then from 1.25.21 to 1.27.3. However, please note that my test environment was simple and not representative of more complex use cases.
Alternatively, if you find this process too complicated, you could spin up a new cluster with the latest version (1.27.3) and migrate your data from the old cluster using the migration scripts available on our website. If you have a small amount of data, the migration should only take a few minutes.
I hope that helps