Can not delete all objects

Dear community, I have got an interesting behaviour in HA Weaviate cluster, here is what we have done:

  • we deleted big number of objects
  • after that, we do a search and we still see ~ 1.7K objects, which we have deleted
  • the number of found objects returned from the search is different (+/- 100 objects) - it looks like it depends on which cluster node the request ends

I’ve gone trough the CAP implementation consideration in Weaviate, but I doubt it is related to eventual consistency as after 24h we still observe the behaviour above.
PS: We use Weaviate Cloud service

Hi @insightloop !

I have escalated this issue with our core team, they are looking into it already.

Thanks for reporting!

1 Like

Do maybe need some additional information? I am happy to provide details if needed.

Thank you.

Hi guys,

Is there any more info on this issue? We are experiencing something very similar:

  1. We added >20k objects
  2. Deleted all of them
  3. Now we have a situation when /v1/objects returns no objects, but vector / hybrid search is still returning results.

The deletion happened over 2 weeks ago, so it can’t be a temporary inconsistency.


I ended up here by looking for some clues on a very similar issues. We are deleting often all documents from a tenant, and then re inserting everything. The amount of documents is way smaller here, something like 80 documents, but today we ended up in a situation where, after deletion, bm25 search and count were returning no results, while hybrid or vector search were.
By count, i mean something like:

{Aggregate { %s (tenant: \"%s\") {meta {count}}} }


This was addressed in recent 1.24+ versions. I will mark this as solved, but don’t hesitate to open a new thread if this issue arises again.