you 9c5ffbfb0c fix: resolve SQLite SQLITE_BUSY write contention in ingestor ...

Three changes to eliminate concurrent write collisions:

1. Add _busy_timeout=5000 to ingestor SQLite DSN (matches server)
   - SQLite will wait up to 5s for the write lock instead of
     immediately returning SQLITE_BUSY

2. Set SetMaxOpenConns(1) on ingestor DB connection pool
   - Serializes all DB access at the Go sql.DB level
   - Prevents multiple goroutines from opening overlapping writes

3. Change SetOrderMatters(false) to SetOrderMatters(true)
   - MQTT handlers now run sequentially per client
   - Eliminates concurrent handler execution that caused
     overlapping multi-statement write flows

Root cause: concurrent MQTT handlers (SetOrderMatters=false) each
performed multiple separate writes (transmission lookup/insert,
observation insert, node upsert, observer upsert) without transactions
or connection limits. SQLite only permits one writer at a time, so
under bursty MQTT traffic the ingestor was competing with itself.

2026-03-28 16:16:07 +00:00

..

ingestor

fix: resolve SQLite SQLITE_BUSY write contention in ingestor

2026-03-28 16:16:07 +00:00

server

perf: precompute distance analytics at ingest time, fixes #169

2026-03-27 22:54:03 -07:00