Skip to main content

Qdrant (qdrant)

Vector database for the embeddings of the retrieval pipelines. Single node or distributed with Raft consensus and sharded collections.

Generated from catalog/services/qdrant.yaml: do not edit by hand.

Summary​

Version1.14.1
Useinstall and configure, configure and connect
Layerfunctional (AI catalog)
CategoryData platforms
Installation methodsbinary, podman
External connectionqdrant
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentqdrant

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
container imagedocker.io/qdrant/qdrantv1.14.1Apache-2.0image key qdrant, used by node, digest sha256:419d72603f5346ee22ffc4606bdb7beb52fcb63077766fab678e6622ba247366
binary archiveqdrant-x86_64-unknown-linux-gnu.tar.gz1.14.1Apache-2.0https://github.com/qdrant/qdrant/releases/download/v1.14.1/qdrant-x86_64-unknown-linux-gnu.tar.gz, x86_64

Images are pinned by tag in the descriptor, and by digest when the descriptor declares one (the offline bundle then refuses a pulled image that does not carry it); the digest is recorded in the mirror of the Manager when the offline bundle is imported, and every pull or load is checked against it.

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)
podmanRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64, aarch64 (not restricted by the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

  • at least 2048 MB of memory (blocking, memory).

Programs the commands and checks of the service start on the host, outside the managed roots: add them to allowed_commands of the agent (see Security of the Navin agent), else the agent refuses them with command_not_allowed: /usr/bin/curl.

Network and ports​

ComponentPort namePortOpened in the host firewall
nodehttp6333/tcpyes
nodegrpc6334/tcpyes
nodep2p6335/tcpyes

Services and connections needed​

This service has no dependency.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory
podman-the container images of the descriptor, run by Podman under systemd

Components​

ComponentKindInstallation methodsPorts
Qdrant node (node)masterbinary, podman6333/tcp, 6334/tcp, 6335/tcp

Single node (standalone) (default)​

One Qdrant node.

What the mode deploys:

ComponentPlacement
nodemin 1, max 1

Distributed (distributed)​

Nodes joined by Raft, bootstrapped from the first node; an odd count keeps the quorum.

What the mode deploys:

ComponentPlacement
nodemin 3, odd number, recommended 3

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select Qdrant. The card shows the licence Apache-2.0. Pick the Method among binary, podman (default binary). To register an existing qdrant service of your organisation instead, turn on Use an existing external service.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: standalone (default), distributed. Each mode deploys the components listed in Installation methods and modes.

  4. Bindings. This service has no dependency: the Bindings step has nothing to bind.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

Connect an existing service​

Schemeshttps, http
Default port6333
Authenticationoptional
Health check/healthz
Authentication methodFieldsDescription
api_keyapi_keyAdmin key (service.api_key) or read only key (service.read_only_api_key), sent in the api-key header.
jwttokenGranular access token (JWT of service.jwt_rbac) signed with the admin key.
none-Without an API key Qdrant is open to anyone who reaches it: development only.

Official documentation: https://qdrant.tech/documentation/security/

High availability​

Clusternative (native)
High availabilitynative (native)
Failovernative (native)
Replicationnative (native)
QuorumRaft (raft)
Discoverystatic (static)
Entry pointany node (any-node)
Official documentationhttps://qdrant.tech/documentation/distributed_deployment/
Peer TLS parametertls_enabled
Cluster status commandcluster_info

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
standalonestandalone (standalone)single (single)-1One Qdrant node.
distributedcluster (cluster)active-active (active-active)node3Nodes joined by Raft from the first node; collections created with a replication factor of 2.

Notes​

  • Qdrant OSS needs an explicit configuration of the replication and of the shard rebalancing: it is not the managed high availability of Qdrant Cloud. The catalog sets a default replication factor of 2 for new collections; moving shards after a node change is an operator action.

Configuration parameters​

Network​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
HTTP port (http_port)port6333-nononoPort of the REST API and /metrics.
gRPC port (grpc_port)port6334-nononoPort of the gRPC API.
Peer port (p2p_port)port6335-nononoPort of the internal traffic between nodes (distributed mode).

Storage​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Payload on disk (on_disk_payload)booltrue-nononoKeep payloads on disk to save memory.
Shards per collection (default_shard_number)int1min 1, max 64nononoDefault shard count of new collections, one per node. (recommended len(topology.node))

Security​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
TLS (tls_enabled)boolfalse-nononoServe the APIs and the peer traffic over TLS with the manager CA certificate.
API key (api_key)passwordgenerated-noyesnoKey required by every API call.

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
httphttpnode6333 (http_port)-tls_enabled-api_key-
grpcgrpcnode6334 (grpc_port)-tls_enabled-api_key-

Commands​

CommandComponentTargetDescription
Cluster status (cluster_info)nodeevery hostChecks the Raft state and the peers seen by every node.

Health checks​

Liveness (per instance)​

ComponentCheckDetails
nodeHTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn }}:{{ config.http_port }}/healthzExpected 200; 60 retries

Readiness (service check)​

CheckDetails
HTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn }}:{{ config.http_port }}/readyzExpected 200

Preflight checks​

CheckTypeMeaningSeverityComponents
memorymemory_mb {"min": 2048}at least 2048 MB of memoryblockingevery component
http_port_freeport_free {"param": "http_port"}port 6333 free on the hostblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.data }}, {{ paths.log }}.

  • Web UI: {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn }}:{{ config.http_port }}/dashboard

Upstream documentation​