-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
request failed: 408 #564
Comments
You might be spinning up too fast or might have exceeded your linode limit @marcelo321? |
Linode has a 10 requests per 30 seconds limit on creation calls from what I am reading. I am playing around with modifying the sleep time in the fleet file to find a consistently working number on there. I may try to add the rate limits to the provider files with each limit and modify the fleet script to pull from there and toss it in as a PR to see if it can help with this. |
There might be more issues in axiom-init, Line 267 in 2a80808
Line 246 in 2a80808
We might not want to background these processes. Ty for looking into it @fail-open. Lmk what you come up with. |
I think I might be answering the wrong thing. Initializing too many calls in one go I believe throws a 429 vs a 408. I was answering for 429 so I am not helpful here. This is what I had found regarding 429s at least that I was typing up before I realized this was a different code On linode 3 second (for 10 in 30 seconds) still threw an error, likely right on the thresh hold. 4 seconds I was able to spin up 50 and everyone of them successfully launched. Looking at Digital Ocean, their model seems to allow for much faster, 250 a minute, 5000 an hour, but you will get 429 if you try to do more during a 1 hour window. Can see this count in the response headers.
|
With the changes in axiom-fleet to increase the sleep time between calls, I dont get 429 anymore, but now I do see 408s on linode. Trying to look into it more |
I asked linode and they said 408 is still a rate limit but did not give much extra guidance other than slow down a little more. I am still learning axioms code and assumed that it was doing one call per spin up so figured 4 seconds would be good, and seemed to be so when I tested yesterday, but maybe there are other calls happening to facilitate? |
@marcelo321 @fail-open @osamahamad thanks for the input! With the latest change to init_sleep for Linode, I've been consistently able to spin up fleets of 100+. Going to close this issue and #555. Please let me know if you disagree. Thanks again!
|
Hi, getting this error in linode:
The text was updated successfully, but these errors were encountered: