Stream: inferno
Topic: BDE-07 180 second timeout
Bill Findeisen (Sep 15 2021 at 01:32):
The bulk data group export status check fails if the hard coded 180 second timeout is reached. Is this value derived from any where in the specification? There are a lot of variables that can come into play and this value does not seem configurable.
Yunwei Wang (Sep 15 2021 at 13:47):
I cannot remember why we decided the timeout defaulted to 180 seconds. Testing client cannot wait forever while server preparing export files so we have to pick a timeout threshold. How long does your server take to complete exporting?
Cooper Thompson (Sep 15 2021 at 13:54):
We have struggled with that timeout as well. We've managed to get by, but an increased timeout would be nice for us as well. Maybe default to 180, but have an option to specify a manual override in the frontend UI?
Bill Findeisen (Sep 15 2021 at 14:54):
Yunwei Wang said:
I cannot remember why we decided the timeout defaulted to 180 seconds. Testing client cannot wait forever while server preparing export files so we have to pick a timeout threshold. How long does your server take to complete exporting?
It varies depending on the amount of data. It would be nice if it was overridable through ui perhaps.
Yunwei Wang (Sep 15 2021 at 14:56):
@Bill Findeisen @Cooper Thompson Thank you for the feedback. I created a GitHub issue to track this request. https://github.com/onc-healthit/inferno-program/issues/359.
I think one possible reason could that if the server does not include 'retry-after' header in status response, Inferno calculate the wait time using exponential backoff suggested by Bulk Data IG. So the wait time increases really fast.
Moin Syed (Sep 21 2021 at 15:05):
We face similar issue, need an option to customize the time out.
@Yunwei Wang You did mention about "retry-after", we do send it but still we have 180 second timeout.
Further the response header in inferno is shown as "retry_after" even though we send it as "retry-after"
Yunwei Wang (Sep 22 2021 at 22:03):
@Moin Syed We will add a UI configuration for the timeout settings.
If the server does not reponde with retry_after header, Inferno uses 'exponential backoff' to calculate the waiting seconds, which is 2 ^ n - 1. Though the default setting is 180 seconds, using exponential backoff times out after 120 seconds. Because 1+3+7+15+31+63=120, the next waiting time is 127 seconds and 120+127 > 180.
Moin Syed (Sep 24 2021 at 03:23):
@Yunwei Wang I have provided retry_after value as 10, it checks for every 10 seconds but after 180 seconds in total it will again timeout. Irrespective of the retry-after value, it is timing out in 180 seconds now.
Yunwei Wang (Sep 24 2021 at 13:05):
Yes, the default is 180 seconds.
Last updated: Apr 12 2022 at 19:14 UTC
