I am experiencing gateway time-outs on export storage sync requests for some of my larger projects.
This happens regardless of whether I use the web GUI or the API via /api/storages/export/localfiles/{storage_id}/sync.
I tried increasing the timeout, but can't seem to go longer than 90 seconds that no matter what I put in the POST request.
Of note, when I sync via the GUI, the syncing process will keep running on the backend even after the 90 second timeout. However, there's nothing in the logs that signal when it's complete. I have to keep calling /api/storages/export?project={project_id} and check if status = completed. Not ideal.
I see two possible solutions to this problem:
Increase the timeout (we should be able to do this; maybe with a flag to the nginx docker?)
When calling from the API, make sync continue on the backend even after it times out (this is a bug).
I am experiencing gateway time-outs on export storage sync requests for some of my larger projects.
This happens regardless of whether I use the web GUI or the API via
/api/storages/export/localfiles/{storage_id}/sync
. I tried increasing the timeout, but can't seem to go longer than 90 seconds that no matter what I put in the POST request.Of note, when I sync via the GUI, the syncing process will keep running on the backend even after the 90 second timeout. However, there's nothing in the logs that signal when it's complete. I have to keep calling
/api/storages/export?project={project_id}
and check ifstatus = completed
. Not ideal.I see two possible solutions to this problem:
Thanks,
Willie