chromadb

ChromaDB stop sequence ignored during disaster recovery

by
cable network

Problem – Stop Sequence Ignored During Disaster Recovery During a disaster‑recovery (DR) operation on a multi‑node ChromaDB cluster, the configured stop_sequence was not honoured. The restoration process continued past the intended termination point, resulting in: Partial overwriting of existing embedding files. Duplicate document IDs across shards. Truncated vectors – up to 12 % of dimensions lost … Read more

ChromaDB container crash loop on-premises OOM error

by
photo of computer cables

Problem – ChromaDB Container Crash Loop on‑Premises OOM Error Deployments of ChromaDB on shared on‑premises servers often encounter a crash loop where the Docker container is repeatedly killed and restarted. Typical symptoms include: Docker daemon reports OOMKilled for the container. Health‑check failures such as HTTP 500 Internal Server Error from the /healthz endpoint. Docker logs … Read more