-
Notifications
You must be signed in to change notification settings - Fork 157
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
fast export impl 'txTimeoutMillis' should be set relative to the configured transaction timeout #2150
Comments
@lmsurpre I added a configuration element for this, I just didn't plug it in. |
I spent some time looking at this... One, we could read from the variable FHIR_TRANSACTION_MANGER_TIMEOUT, however that's not a guarantee to be a number. We could interpolate the timeout using an SPI, I played with this a bit, it's not super clean, and requires reflections. Some alternatives that were mentioned on StackOverflow: |
I think we should just go with the user-configured approach and document that it must be less than the configured transaction timeout. |
Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
configure the maxChunkReadTime for Fast Export and configurable timeout for presigned URL #2150
I set
I also purposefully misconfigured the system by keeping maxChunkReadTime at 15s and setting FHIR_TRANSACTION_MANGER_TIMEOUT to
|
Describe the bug
The fast export impl has a hardcoded "read window" of 90 seconds:
If users have overridden the transaction timeout, this could result in failure.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the system export succeeds
Alternative idea
Check if it's possible to override the configured transaction timeout value (programatically or via bulk datasource config).
If so, we could set it to 120s for just the export transaction (without affecting anything else).
Additional context
Perhaps related to #2149
The text was updated successfully, but these errors were encountered: