menu

Flyio

Talk about Fly.io's product Global Application Platform - Support and operational questions should go to [email protected]

Channels
Team

Are configured regions active all the time?

May 27, 2020 at 5:05am

Are configured regions active all the time?

May 27, 2020 at 5:05am

May 27, 2020 at 5:26am
Only the regions with VMs running are active, the rest are available when more VMs start. For example, an app might have 3 regions allowed but only 2 VMs running
  • reply
  • like
you can see where VMs are running with the flyctl status command
  • reply
  • like

May 27, 2020 at 1:41pm
ah right
  • reply
  • like
So I imagine there is at least one active region at any time that will satisfy requests until a new region needs to be activated. Is this correct?
  • reply
  • like
I used flyctl status and it says the 4 configured regions are running. Which is a bit weird since this app has no traffic at all.
4adf49a5 5 ams run running 1 total, 1 passing 0 8h48m ago
1cde4bd0 5 iad run running 1 total, 1 passing 0 8h48m ago
1d0e04e4 5 lax run running 1 total, 1 passing 0 8h48m ago
da2ab931 5 mrs run running 1 total, 1 passing 0 8h49m ago
  • reply
  • like
And also because only 3 regions are configured:
Allowed Regions:
ams Amsterdam, Netherlands
iad Ashburn, Virginia (US)
lax Los Angeles, California (US)
  • reply
  • like
What does flyctl scale show say?
  • reply
  • like
Scale Mode: Standard
Min Count: 4
Max Count: 10
VM Size: micro-2x
  • reply
  • like
There's your answer, the min count is 4 with 3 regions in the pool. The system is fulfilling the min count by deploying in a region close to but not in your region pool. flyctl scale set min=3 should get you to what you are expecting
  • reply
  • like
Thanks I'll read the docs to understand better how those settings work.
  • reply
  • like
btw you have a 404 in your docs https://fly.io/docs/flyctl/autoscale/
  • reply
  • like
it's the link from the cli that says "Configuring autoscaling"
Edited
  • reply
  • like
so I reduced the scaling to 3 as you suggested.
  • reply
  • like
Ah, I'll fix that. Autoscaling control moved to the scale command.
  • reply
  • like
And yes, I see now only 3 regions are active...
dc1c88d7 9 ams run running 1 total, 1 passing 0 29m8s ago
8f43d042 9 lax run running 1 total, 1 passing 0 28m30s ago
c2f8a1d2 9 sjc run running 1 total, 1 passing 0 29m28s ago
But these are not the configured regions:
Allowed Regions:
ams Amsterdam, Netherlands
iad Ashburn, Virginia (US)
lax Los Angeles, California (US)
  • reply
  • like
is there a way to stop and restart the application?
  • reply
  • like
Edited
  • reply
  • like
Right now, you can make it redeploy by doing something like "flyctl secrets set NOTASECRET=nosecret"
  • reply
  • like
This will add a secret and, because of Fly's versioning mechanism, it will trigger a redeploy
  • reply
  • like
couldn't I just deploy the application again?
  • reply
  • like
would that solve the regions mismatch?
  • reply
  • like
You could.... (I just find the secret trick is quicker right now....)
  • reply
  • like
yep that fixed it!
  • reply
  • like

May 31, 2020 at 6:53pm
For some reason this keeps happening...
  • reply
  • like
def03587 3 dfw run running 1 total, 1 passing 0 2m28s ago
8cce24f5 3 ewr run running 1 total, 1 passing 0 1m25s ago
ddfe2060 3 yyz run running 1 total, 1 passing 0 2m54s ago
Allowed Regions:
dfw Dallas 2, Texas (US)
ewr Parsippany, NJ (US)
lax Los Angeles, California (US)
  • reply
  • like
Show more messages