## TL;DR

Did an update collection to generate embeddings with ts/all-MiniLM-L12-v2 5. Next I did a restart on typesense-server.

## Steps

1. What was reported:
Issue typesense/typesense#1507 (closed, 17 comments): ## Description Trying some experiments (Round 1): 1. Started with a "fresh" server (clone of an existing production) 2. Upgraded TS to 0.25 3. Target is a collection with around 18K docs (post, articles etc) 4. Did an update collection to generate embeddings with `ts/all-MiniLM-L12-v2` 5. Server has been churning away since then for 18 hours 6. API calls to this collection dont complete (as expected) while calls to other collections do complete, also as expected 7. Which means that TS is working fine, and its not crashed 8. Next I did a restart on typesense-server.

2. What works:
The stall was memory pressure, not a crash: generating embeddings for an already-populated collection needs far more RAM than normal indexing. The reporter solved it by moving to a larger server class and succeeded with Typesense 0.26.0, about 20K documents, and the `gte-small` model, finishing in roughly 35 minutes. Practical steps: size the box up before altering a populated collection to add an embedding field, use a current Typesense release, and pick a small embedding model. Altering an empty collection is instant either way, so it is also fine to create the embedding field first and index documents after.

## When to use

You are seeing this: What was reported: Issue typesense/typesense#1507 (closed, 17 comments): ## Description Trying some experiments (Round 1): 1. Use this skill when you run into "Trying to generate embeddings using in-built".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Typesense 0.26.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_WvwPxsCl5HoRhKsZTIfvRg/versions/skv_FIpxL9vA3um4Gq0Gs79Gjg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_WvwPxsCl5HoRhKsZTIfvRg>
- Current Markdown URL: <https://vectle.com/skills/skl_WvwPxsCl5HoRhKsZTIfvRg/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/typesense/typesense/issues/1507"
  ]
}
```
