Cluster State Unhealthy on Restart with Large Collection
TLDR Julian experienced an unhealthy cluster state on restarts with a large collection. Jason explained that it's expected, and suggested running the cluster persistently like Redis.
1
Apr 21, 2023 (5 months ago)
Julian
04:53 PM155892 queued writes > healthy read lag of 1000 (counting down). The health endpoint only return ok: true once the queued writes are finished. Happens over again on every restart. Am I doing something wrong here? Any hints are appreciated ๐
Jason
05:42 PMJulian
05:44 PMApr 22, 2023 (5 months ago)
Jason
11:59 AMJulian
12:23 PM1
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Debugging and Recovery of a Stuck Typesense Cluster
Charlie had a wedged staging cluster. Jason provided debugging and recovery steps, and Adrian helped with more insights. It turns out the issue was insufficient disk space. Once Adrian increased the disk size, the cluster healed itself.
Investigating Unhealthy Cluster and Typesense Issues
Gustavo reported an unhealthy cluster, which Jason identified was due to stalled writes from OpenAI's API. The cluster was temporarily stabilized by downgrading to RC35, but a full resolution is still pending.
Slow, High CPU Write Operations After Collection Drop in Typesense
Himank discussed an issue in Typesense where deleting and recreating a collection led to slow write operations and high CPU usage. Kishore Nallan suggested using an alias to avoid this issue. Numerous tests and debugging was conducted as pboros contributed with local testing. Kishore Nallan aimed to start implementing a range delete and full db compaction after deletion to potentially solve the issue.