mirror of
https://github.com/qdrant/qdrant.git
synced 2026-10-03 03:17:43 -05:00
Arnaud GourlayandClaude Opus 5
bee66e82e1
The reload inventory resolved the custody fork's first branch: the lost point's last durable holder reloads fine, directory present, expected version, expected point count minus one. What remains unobserved is the pre-close side at segment granularity: which directory's in-memory state held the point at close, under what durability claim. The failing hop's ledger line says the source was clean at version==persisted while its reloaded directory lacks the point, which, if confirmed against a placement snapshot, is a flush whose durable content does not match its claim. Capture the placement of every visible point (segment, directory, point version, deferred flag, segment version/persisted) right before stop_gracefully and print it for every id the reload loses. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>