Hi everyone, On our development instance , I see the following stats :

{
  "delete_latency_ms": 0,
  "delete_requests_per_second": 0,
  "import_latency_ms": 0,
  "import_requests_per_second": 0,
  "latency_ms": {},
  "overloaded_requests_per_second": 0,
  "pending_write_batches": 428,
  "requests_per_second": {},
  "search_latency_ms": 0,
  "search_requests_per_second": 0,
  "total_requests_per_second": 0,
  "write_latency_ms": 0,
  "write_requests_per_second": 0
}

What does the value for pending_write_batches mean here ? Does it imply that there are 428 batches yet to be written to respective collections ?

That's exactly right... That number should go down over time though as the data is being processed

Is there a way to clear this if it remains stuck for some reason ?

There's no way to clear writes once they enter the queue. If it's stuck it's usually either due to resource constraints (memory or disk), in which case upgrading capacity will help. In older versions of Typesense, we did have a few bugs here and there where some invalid data will choke up the write queue. So I would recommend upgrading to

v28.0.rc35

first to see if that fixes the issue

Could this lead to indexing failures(Request Malformed 400 error) in subsequent iterations ? I've been seeing the same for a few collections, that usually fail after about 400-500 items getting indexed( I use batches of 40).

No 400 responses are unrelated