microsoft / microsoft/fhir-server
The SQL Operation Timeout should be configurable
Nobody has claimed this yet.
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
**User story**
As an operator, I want to be able to configure the SQL command timeout so that long-running search operations will not run into a timeout, and return a 500 error code (#1452).
**Acceptance criteria**
1. When I configure the SQL command timeout to a value larger than 30s, then queries running longer than 30s (which is the default timeout for SqlCommand) shouldn't time-out.
It could be implemented similar to the convert operation timeout: https://github.com/microsoft/fhir-server/blob/main/src/Microsoft.Health.Fhir.Shared.Web/appsettings.json#L82
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/Microsoft.Health.Fhir.Shared.Web/appsettings.json around the convert operation timeout referenced in the issue, then follow the SQL command timeout used by search operations. Configure a value above 30 seconds and verify that queries running longer than the default 30-second timeout complete without returning a 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100