-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTG-1110 Add request time out for DB query #362
MTG-1110 Add request time out for DB query #362
Conversation
andrii-kl
commented
Jan 14, 2025
- Added configurable timeout for database queries in the API service.
- Added new test cases to verify the behavior of the timeout mechanism.
- Added a readme file with a second option for a global query execution time limit.
- Added configurable timeout for database queries in the API service. - Added new test cases to verify the behavior of the timeout mechanism. - Added a readme file with a second option for a global query execution time limit.
- Fix Lint issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mostly spelling comments
- Implemented suggestions from the PR review. - Added readme file with some tips.
- fix code format
- minor code style fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How will postgres behave with this change? Will it terminate a query? We've had issues with PG, still executing some query after a day of the container restart... That was a heavy COPY FROM that was not even killable, but still.
Also WDYT of injecting ?statement_timeout=
into the connection string on the relevant services (ingester, api)?
It is definitely worth adding this option |
Co-authored-by: Oleksandr Mykhailenko <[email protected]>
Another approach with db url parameter config |