With the hobby plan is it possible to scale memory higher than the 256 free allowance?

1

Hey team,

I’m on the hobby plan and trying to do:

➜  flyctl scale memory 512 --app neto
Updating machine 2865539b6e53e8
No health checks found
Machine 2865539b6e53e8 updated successfully!
Updating machine 9185e0db672118
Error: could not update machine 9185e0db672118: failed to update VM 9185e0db672118: aborted: could not reserve resource for machine: insufficient memory available to fulfill request

It’s not obvious from the different docs whether I can or cannot do it on the hobby plan:

Any hints appreciated :pray:

2

Yeah, you can scale everything beyond the free allowance, but you do have to pay for it.

2 Likes
3

Thanks!

I’ve added my credit card to the account, so I assume this should be working then and maybe it’s a transient error/bug. Or do I need to add some credits first? :thinking:

4

It’s working for me, so idk. It looks like it worked for one of your machines but not both, so you could try it again or destroy the one that failed and clone the successful one.

1 Like
5

Oh right, thanks for the hint! I also saw the other machine being stopped at some point, maybe that’s why.

Thanks for sharing, at least I know now on which track I am :pray:

6

The insufficient memory available to fulfill request error is an us problem, not a you one. It means that we don’t have capacity to place a machine with that much memory in the region you’ve selected (in this case mad). Can you try deploying to a different region?

2 Likes
7

Hey @DAlperin, thanks for checking the issue!

I finished working around it by destroying the stopped machine:

(venv) ➜  neto git:(main) fly scale show                    
VM Resources for app: neto

Groups
NAME    COUNT   KIND    CPUS    MEMORY  REGIONS 
app     2       shared  1       256 MB  mad(2)  

(venv) ➜  neto git:(main) flyctl scale memory 512 --app neto
Updating machine 9185e0db672118
Error: could not update machine 9185e0db672118: failed to update VM 9185e0db672118: aborted: could not reserve resource for machine: insufficient memory available to fulfill request

(venv) ➜  neto git:(main) flyctl machine destroy 2865539b6e53e8
Error: machine 2865539b6e53e8 currently started, either stop first or use --force flag

(venv) ➜  neto git:(main) flyctl machine destroy 9185e0db672118
machine 9185e0db672118 was found and is currently in stopped state, attempting to destroy...
9185e0db672118 has been destroyed

(venv) ➜  neto git:(main) fly scale show                       
VM Resources for app: neto

Groups
NAME    COUNT   KIND    CPUS    MEMORY  REGIONS 
app     1       shared  1       512 MB  mad

I’ll keep the different region in mind in case I run into it again, thanks!

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.