A bit strange.. now it feels like its a little bit...
# community-help
t
A bit strange.. now it feels like its a little bit more OK for some other collections.. so maybe its embedding collections specifically that have problem? Anyway.. I will re-create and fill with data and report back if it behaves the same or not again. Just wanted to share in case it ringed some bell for devs if any part of code is touched that can affect this somehow between rca releases.
k
Thanks, if you can reproduce the issue with the collection with embeddings, that will be great.
t
Yes, will try again after I have filled it.. Hopefully later today and let you know how it behaves this time.
h
Hi @Thomas Andersson do you have any async_reference field in your collections?
t
Yes I do
h
Is the collection that took more time to drop being referenced by some other collection?
We made https://github.com/typesense/typesense/pull/2682 change recently that I can imagine slowing the drop operation.
t
yes it is.. then good, then there is some reason for it. Thanks for looking into it. And then its my own fault as I did the original issue that PR was based on 🙂
Maybe there is some optimization to do.. but otherwise if its only affecting drop, then I guess its not critical.. not something we do in production very often.
h
https://github.com/typesense/typesense/pull/2718 This should fix the regression.
t
Nice, I saw the PR! Will there be a new rca on dockerhub soon with it?
a
@Kishore Nallan could we build a rca36?
t
Just ping when available and I will test it out.
k
Published
30.0.rca36
that contains the patch.
t
Very nice, just tried and now its blazing fast to drop collections again.
k
Thank you for confirming.