-
Notifications
You must be signed in to change notification settings - Fork 7
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
AMDA get_data never returns on long requests #40
Comments
Reading this issue makes me think about introducing a |
In AMDA, when a "getParameter" request time is greater than 4 minutes, the execution enter in a batch mode. In this case, the result will look like:
In this condition, getStatus API can be used to retrieve the status.
It seems that Speasy does not implement this scenario. For information, our AMDA backend is behind a proxy with a timeout defined as 5 minutes. This is why we need to enter in a "batch mode" when the execution of a request is "too long". |
@brenard-irap we can use this from REST API now? |
@jeandet Yes |
Ok, I propose to work on that during next week workshop. |
Keep in mind that when timeout is reached the "batch mode" task is created on the server. This means that if a user interrupts speasy while its getting data, the task will keep running on the server, this is why I don't like the timeout solution. Another simple way of dealing with this problem is to raise an Exception if a timeout is reached. The value of the timeout needs to be smaller than the 4 minutes used by AMDA. |
PR #41 |
Description
AMDA creates background jobs to deal with requests that take too long to answer (timeout exceeded). Speasy is not notified of this fact, thus when trying to retrieve a large dataset the
get_data
method may never return, it will wait indefinitely.What I Did
Solution
Modified the
dl_parameter
function inspeasy.webservices.amda._impl
module :The text was updated successfully, but these errors were encountered: