Add DB retry/backoff and improve logging#37
Merged
Conversation
Improve resilience and observability around DB access and GraphQL requests. - Add environment constants EXO_DB_RETRY_MAX, EXO_DB_RETRY_BASE_MS, EXO_DB_RETRY_MAX_MS. - Implement retry/backoff logic for read-only (SELECT) SQL operations with configurable max retries, base and max backoff, jitter, and detailed error logging for Postgres errors. - Add RetryConfig and helper functions to detect transient SQL errors and compute backoff. - Log and map transaction start failures to DatabaseError with tracing error context. - Warn and drop closed DB client in TransactionState before reacquiring. - Emit detailed error info when failing to acquire a pooled DB client (pool status + error) instead of silently propagating. - In GraphQL router: extract request ID from common headers, add it to Sentry scope, create a tracing span per request and log receipt. These changes aim to handle transient DB connectivity issues more robustly and give better diagnostics for DB and request lifecycle failures.
|
Version bump detected: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve resilience and observability around DB access and GraphQL requests.
These changes aim to handle transient DB connectivity issues more robustly and give better diagnostics for DB and request lifecycle failures.