Operations

← Handbook index

Result archive database

The archive_results_db sink is the long-term home of every search result. It writes to the shared Postgres server and keeps a larger connection pool than the hot database, because every result lands there while only high-match results reach the hot one.

When this sink reports delivery errors, check the Postgres service first: the pipeline keeps consuming, and failed batches are not replayed, so a long outage is visible as a gap in the archive rather than as a stalled worker.

Daily checks

• Consumer lag on search-requests is flat or falling.
• No sink circuit breaker is open on the dashboard.
• The DLQ topic is empty; anything in it names its own failure reason.