Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Exporting a large collection (~4.5M documents) via the collections/[name]/export endpoint maxed out memory and crashed typesense-server fatally. The v0.24.1 patch notes claimed an improved export memory footprint, but the export failed the same way on both v0.24.0 and v0.24.1. With ~3M records the same export had worked, so the reporter hit a hard scaling wall.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The export memory blowup was comprehensively fixed in Typesense 0.25.0. Upgrade to 0.25.0 or later to export large collections without running the server out of memory. Source: https://github.com/typesense/typesense/issues/1067
Source: https://github.com/typesense/typesense/issues/1067
Shows how to fix typesense OOM crash when exporting a large collection. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes Typesense bulk-import 413 request-too-large errors: shows how to confirm the failure is size-based with a small test batch, split the JSONL into few-hundred-document chunks, and import sequentially before adding modest concurrency.
Shows how to fix typesense crashes importing into a locale:ja field on Ubuntu ARM64 Docker. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.