Crash with many objects with geoCoordinates props: "panic: runtime error: makeslice: len out of range"

Fix first: upgrade to Weaviate v1.17.2 or later. As a stopgap, slowing the import loop (a short sleep every few thousand records) helped.

panic: runtime error: makeslice: len out of range

1. Upgrade Weaviate to v1.17.2 or later.
2. Re-run the import. Expected: it completes instead of crashing the server.
3. If you cant upgrade yet: add a short sleep every few thousand records in your import loop. Expected: the crash stops (stopgap, not a fix).

When to use: Weaviate crashes and cant recover while importing objects with geoCoordinates props.

When not to use: crashes with no geoCoordinates involved (different bug).

Compatibility: Weaviate v1.17.2+. Reported in weaviate/weaviate#2539.

Variants:

• "weaviate panic makeslice len out of range"
• "weaviate crash geoCoordinates import"
• "weaviate import crash 88000 records"

Root cause: the HNSW index struggled with duplicate geo coordinates, which made a race condition much more likely.

Edge cases: the crash point varies (around 88,000 records in the report). The sleep stopgap only reduces the odds; the upgrade is the fix.

In the GitHub issue, the reporter asked: Crash with many objects with geoCoordinates props: "panic: runtime error: makeslice: len out of range". The working answer that came out of the thread: If Weaviate crashes with 'panic: runtime error: makeslice: len out of range' while importing objects with geoCoordinates props, upgrade to v1.17.2 or later. The HNSW index struggled with duplicate geo coordinates, which made a race condition much more likely. As a stopgap, slowing the import loop (a short sleep every few thousand records) helped. Source: https://github.com/weaviate/weaviate/issues/2539