We use a workflow where we replace indices by crea...
# community-helpj
John
05/08/2023, 9:40 AMWe use a workflow where we replace indices by creating a new one, repointing an alias, and then deleting the old index. After upgrading our Typesense server to 0.25.0.rc25, we've started to have issues deleting old indices. Against our production instance I can reproduce that
• When querying for all collections, collection "foobar123" is there.
• When trying to delete it, I get
No collection with name "foobar123" found.k
Kishore Nallan
05/08/2023, 9:43 AM1. What version of Typesense were you using before the upgrade?
2. What happens when you restart the Typesense process?
Kishore Nallan
05/08/2023, 9:46 AMThe interesting thing here is that both get all collections API and the delete collections API use the same structure for accessing the list of collections. So I am not sure how one doesn't find it.
j
John
05/08/2023, 9:49 AMAha, I just now noticed that after getting the
No collection with name "foobar123" foundk
Kishore Nallan
05/08/2023, 9:49 AMDoes your collection name maybe have some special characters?
j
John
05/08/2023, 9:49 AMSo my problem is probably resolved by just catching the 404 and assuming that it was deleted anyway.
k
Kishore Nallan
05/08/2023, 9:50 AMWhat could be happening is also a race condition between issuing a deletion request and then checking for the collection's presence. One of the nodes could lag just a few seconds and if you query that collection then it could momentarily return the collection as present.