# Can not delete all objects

**URL:** <https://forum.weaviate.io/t/can-not-delete-all-objects/913>\
**Category:** Support\
**Created:** [November 6, 2023, 5:01pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913 "2023-11-06T17:01:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![insightloop](https://avatars.discourse-cdn.com/v4/letter/i/73ab20/32.png) [@insightloop](https://forum.weaviate.io/u/insightloop)\
**Post date:** [November 6, 2023, 5:01pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/1 "2023-11-06T17:01:31Z")

</div>

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](https://weaviate.io/developers/weaviate/concepts/replication-architecture/consistency), but I doubt it is related to eventual consistency as after 24h we still observe the behaviour above.  
PS: We use Weaviate Cloud service

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [November 7, 2023, 12:35pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/2 "2023-11-07T12:35:17Z")

</div>

Hi @insightloop !

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

Thanks for reporting!

---

<div class="post-metadata">

**Author:** ![insightloop](https://avatars.discourse-cdn.com/v4/letter/i/73ab20/32.png) [@insightloop](https://forum.weaviate.io/u/insightloop)\
**Post date:** [November 8, 2023, 3:19pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/3 "2023-11-08T15:19:13Z")

</div>

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

Thank you.

---

<div class="post-metadata">

**Author:** ![mickxm](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickxm](https://forum.weaviate.io/u/mickxm)\
**Post date:** [December 28, 2023, 9:58pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/4 "2023-12-28T21:58:59Z")

</div>

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.

Thanks!

---

<div class="post-metadata">

**Author:** ![kRs](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/krs/32/820_2.png) [@kRs](https://forum.weaviate.io/u/kRs)\
**Post date:** [January 11, 2024, 9:18pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/5 "2024-01-11T21:18:43Z")

</div>

Hi,  
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:

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

```

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [March 20, 2024, 6:54pm UTC](https://forum.weaviate.io/t/can-not-delete-all-objects/913/6 "2024-03-20T18:54:32Z")

</div>

Hi!

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.

Thanks!