hi i get this error { \"message\": \"Not Ready or Lagging\"} when i try to delete my collections. Do you know what may cause this issue?

This indicates the the node is lagging behind in writes.

also, sometimes i get this message during import:

I'm not sure about the other

forcibly closed

error. It indicates that the server has closed the connection with a

RST

packet, but it can also mean that some form of client / tcp timeout causing a connection drop. Finally (and least likely), check if the server itself crashed.

@Kishore Nallan server is alive, but still responds with {     "message": "Not Ready or Lagging" } for several minutes already

Is this on Typesense cloud or self hosted?

selftr hosted

What do the logs say?

i'll try again and see if it repeats

Okay, the server will be logging offsets -- if you can send a few lines of that, we can tell how big the lag is. But the problem is essentially about server lagging behind ingesting new data. I presume this is happening during updates, correct?

during upsert

The writes are lagging behind, that is you are pushing upserts too fast and that is exceeding the write lag threshold configuration of 1000. See this snippet in the log line:

last_index index: 29278 ... applying_index: 27909

hmm i see... Is it safe/ok to increase this threshold parameter?

To solve this, increase the

--healthy-read-lag

and

--healthy-write-lag

values to higher values. This way the server won't reject writes.

okay, i will try, thank you

It depends on your business use case. If a bit of lag makes no difference to your business, then it makes no difference.

thank you!