Doing a load test for 5 minutes does not trigger autoscaling even with multiple warnings from the proxy: 2022-07-25T18:32:43Z proxy[eb2ee7d6] ams [warn]Instance reached connections hard limit of 25 2022-07-25T18:32:43Z proxy[eb2ee7d6] ams [warn]Instance reached connections hard limit of 25 2022-07-…

The fix has been deployed, so autoscaling should be working for any future deployments now :rocket:

Just to ensure I wasn’t crazy, I created yet another app to duplicate the behaviour. Ran the following commands and only did a single deploy. Same behaviour. fly scale memory 512 fly regions add ams fly regions add mia fly autoscale balanced min=2 max=7 fly deploy -i registry.fl…

Thanks for reporting this, we’re looking into it and will keep you posted!

Thanks. I even took out the env and experimental blocks and re-ran, but still same behaviour.

I think I found an internal bug possibly causing this issue, and I’ve updated your instance definitions with a tentative fix. Could you do another load test on the running instances (without re-deploying) and let me know if it works this time?

Re-ran test, still no scaling on testmysql.

It is scaling correctly on the 2nd one I deployed. It’s up to 5 instances now. Takes about 2 minutes to detect I think, wasn’t really timing it.

The 2nd app is scaling correctlly. Takes about 60-90 seconds to come up. Scale down takes about 10 minutes. Is that the expected behaviour? testmysql is borked in some strange fashion. The logs show that deployments are being attempted and at a very quick pace to scale up, but no instances actually…

Thanks for the additional testing! I’ll work on rolling out the fix more permanently. The autoscaling service is designed to scale up quickly and scale down slowly with a scale-down lag of 10 minutes, so yes that’s the expected behavior. I think the remaining problem with testmysql may be a separa…

OK, please let me know when the fix is out. I’m still porting, so I’ll leave these up for you to test/debug with if necessary for the next few days. Also, another potential bug. Was testing out machines - created an app called “hora”. The docker deployment was borked, so instead of deleting the …

FYI, there’s a race condition with autoscaling that may be tricky to re-produce. Essentially, the tcp connection health check could fail as it seems traffic gets redirected to the app before the tcp check passes. The vm hits the hard connection limit and will never be healthy at that point. Autosca…

autoscale not scaling

karyakarsa October 10, 2022, 2:39am 16

BTW our app is laravel with nginx, php and supervisor service. is that affect to autoscaling?
I see this thread that make some clue for us