Andrey Vasnetsov

/bounty $200 We would need a way to demonstrate (reproducibly), that the PR actually fixes the issue, and not just makes it less probable

hey @Waseem-k, could you please provide more information about your setup - how do you run qdrant? - What's your collection info looks like? - What kind of queries are...

Have you considered this approach - https://qdrant.tech/documentation/guides/multiple-partitions/ ?

Memory usage you see might be due to disk cache, it is to be expected. I would need a bit more details to answer exactly.

hey @zhangzf875, I am going to close this issue as we can't reproduce the problem without additional information. For the context, here are some more info on proper memory measurement...

Work-in-progress

https://github.com/qdrant/qdrant/issues/3684

Hi @wangludba, could you please provide a bit more details on how to reproduce the issue. Your current description can't really be followed.

WDYT about making `check_collection_name` part of the Claims object? In this case we can track and make sure that all conditions are validated (or some condition was declined).

I don't think making output deterministic would be easy. data placement in segment is random and time-sensitive, and this fact alone will affect the property