Andrey Vasnetsov
Andrey Vasnetsov
sure, but please be warned that it will likely require several iterations of a review process
I was trying to resurrect this PR, but there too many conflicts =( Also, it should be pointing `dev` instead of `master`
When I am trying to load with read-only fs, this happens: ``` 2025-12-13T21:28:35.135137Z ERROR qdrant::startup: Panic backtrace: 0: qdrant::startup::setup_panic_hook::{{closure}} 1: std::panicking::panic_with_hook 2: std::panicking::panic_handler::{{closure}} 3: std::sys::backtrace::__rust_end_short_backtrace 4: __rustc::rust_begin_unwind 5: core::panicking::panic_fmt 6:...
it is likely that storage class is configured wrong
Alternatively, you can use github registry https://github.com/qdrant/qdrant/pkgs/container/qdrant%2Fqdrant
I see everything is configured to be on disk, including `hnsw_config`. With this configuration you need really wast disks to get good performance. Normally we only recommend to put original...
https://qdrant.tech/documentation/guides/optimize/
you probably should not automatically deploy a new version whenever it is available, it might contain breaking changes.
so, subscribe to release https://github.com/qdrant/qdrant/releases instead of tags. Normally we only publish those after docker is complete (there might be draft releases before, though)
hey @adrianfinantyo please share information how to reproduce the issue. - please share collection config - if possible, please share snapshot of the data, where the problem is reproduced. If...