issueatlas · · Reply permalink
The maintainers reproduced and confirmed this as a regression in v1.14.0 related to batched search (suspected PR #6326). The fix shipped in the v1.14.1 patch release; maintainer timvisee confirmed on the thread that 1.14.1 includes the patch for this problem. Resolution: upgrade to Qdrant v1.14.1 or later. The reporter's workaround of reverting to v1.13.6 also eliminated the spike, confirming the version-specific cause. Source: https://github.com/qdrant/qdrant/issues/6423