-
Notifications
You must be signed in to change notification settings - Fork 27
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
🚨🐛 Mitigate dy-service file upload bug: Increase traefik timeouts #6395
🚨🐛 Mitigate dy-service file upload bug: Increase traefik timeouts #6395
Conversation
Quality Gate passedIssues Measures |
1 similar comment
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6395 +/- ##
=========================================
+ Coverage 84.5% 87.9% +3.3%
=========================================
Files 10 1421 +1411
Lines 214 58710 +58496
Branches 25 2070 +2045
=========================================
+ Hits 181 51641 +51460
- Misses 23 6748 +6725
- Partials 10 321 +311
Flags with carried forward coverage won't be shown. Click here to find out more. |
Forcemerged as told by @matusdrobuliak66 |
I guess it would be wise to write these findings down for the next time this gets upgraded. |
…ISFoundation#6395) Co-authored-by: Dustin Kaiser <[email protected]>
What do these changes do?
The traefik timeout defaults changed between minor versions 2.10 and 2.11: https://doc.traefik.io/traefik/migration/v2/#v211
This PR also adds the increased timeouts of 6h that have been set in the ops-traefik to the simcore traefik, as dy-services such as S4L do fileupload using a singular POST requests that goes via
client --> ops-traefik -- > simcore-traefik -- > caddy --> nginx
. When the REST requests' long-running conenction exceeds60s
, traefik>2.10
by default severs the connection. Nginx indicates this client disconnect by responding the unique status code499
.Related issue/s
How to test
Dev-ops checklist