Important bug fix available!

Announcements
1

:triangular_flag_on_post: Important bug fix available :triangular_flag_on_post:

Weaviate Cloud Customers will be automatically upgraded, self-hosters please see below

Today we have identified and fixed a critical bug in Weaviate Core. Under some rare circumstances, this bug can lead to data loss.

Please carefully read the steps below to find out if you are affected and what you can do to upgrade to a fixed version. Affected Versions

The following versions are affected:

  • 1.25.12 to 1.25.19 → fixed in 1.25.20
  • 1.26.2 to 1.26.5 → fixed in 1.26.6

Bug Description

The bug manifests itself in the following ways:

  • Only single-node (non-HA) clusters are affected.
  • Under some circumstances, previous schema changes may accidentally be replayed after a restart.
  • If your schema history contains operations such as “Create Collection,” “Delete Collection,” or “Recreate Collection,” there is a risk that the “Delete Collection” change will be incorrectly replayed, removing all data from the collection.

Mitigation & Upgrade Path

Open Source Users / Self-hosters

If you self-host Weaviate and are currently running one of the versions mentioned above, please upgrade to 1.25.20 or 1.26.6 immediately.

Weaviate Cloud Customers

If you are a Weaviate Cloud customer, there is no action needed from your side. We are currently in the process of updating all affected clusters to a fixed version.

We anticipate that all clusters will have been upgraded within the next 24 hours. Our goal is that before you read this message the cluster has already been upgraded and all data has been validated.

If you need support for your Weaviate Cloud Database, reach out to our team here.

Office Hours

We are also hosting an open Weaviate Office Hours on Wednesday 9am PDT| 12pm EDT | 6pm CEST that you can join and ask all the questions you might have.

Further community support

If you self host Weaviate, please, use this thread for further community support.

Thanks!

3 Likes