Skip to content
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

Increase server timeout limit #23286

Closed
2 tasks done
noahtalerman opened this issue Oct 28, 2024 · 5 comments
Closed
2 tasks done

Increase server timeout limit #23286

noahtalerman opened this issue Oct 28, 2024 · 5 comments
Assignees
Labels
#g-customer-success Customer success issue.
Milestone

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Oct 28, 2024

  • @noahtalerman: Fleet 4.58 added a progress bar for software uploads. User story is here. My understanding is that the current server timeout limit for managed cloud customers (and best practice reference architecture) is 5 minutes. This means that on slower Wi-Fi, users might sit in front of a progress bar for 5 minutes just to see the software upload fail. This is a frustrating experience.

Goal

Bump server timeout limit so that users uploading software on slower Wi-Fi don't sit in front of a progress bar and then see the software upload fail.

We decided that 15 minutes is a reasonable timeout limit to start.

How?

@fleet-release
Copy link
Contributor

In the cloud city,
Timeout increases, uploads
breathe easy, no rush.

@zayhanlon zayhanlon added this to the 4.60.0 milestone Nov 18, 2024
@noahtalerman
Copy link
Member Author

  • Increase server timeout limit to 15 mins in Fleet's best practice reference architecture docs and Terraform

@rfairburn just checking, are there any reference docs (like reference arch) or best practice Terraform that we need to update?

@rfairburn
Copy link
Contributor

I will ensure the reference docs are updated today.

@noahtalerman
Copy link
Member Author

@rfairburn just following up, did you get a chance to check if we need to update reference docs and/or best practice Terraform?

@rfairburn
Copy link
Contributor

#23939 is the relevant PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#g-customer-success Customer success issue.
Development

No branches or pull requests

4 participants