Strange situation: I have a collection with ~70K documents. Whenever I restart my cluster (or in my case my docker container), the cluster state is unhealthy for a couple of minutes. The logs are showing a lot entries

155892 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 🙏

This is expected, since Typesense rebuilds the in-memory index on each process restart, and is unavailable to service requests until this is complete

Understood. Do you have a take on this when doing local development where you might have to reboot your cluster multiple times a day?

I usually just let the cluster run persistently, very similar to Redis

OK, got it. Thanks Jason ✌️