min_machines_running config is ignored?

1

Hi, I’ve been trying out auto-scaling for my clients apps and mostly had it working as expected.
But it seems that the option min_machines_running = 1 gets ignored for most apps and are scaling down to 0 running machines regardless.

Here is my fly.toml (with sensitive stuff such as names removed)

primary_region = "arn"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[env]
  PORT = "8080"

[experimental]
  allowed_public_ports = []
  auto_rollback = true

[[services]]
  http_checks = []
  internal_port = 8080
  processes = ["app"]
  protocol = "tcp"
  script_checks = []
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1

  [services.concurrency]
    hard_limit = 20
    soft_limit = 15
    type = "connections"

  [[services.ports]]
    force_https = true
    handlers = ["http"]
    port = 80

  [[services.ports]]
    handlers = ["tls", "http"]
    port = 443

  [[services.tcp_checks]]
    grace_period = "1s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"

When doing fly status I get a clear list showing that all machines are stopped

Screenshot from 2024-03-05 14-27-51

Is there something obvious that I’m missing? :slight_smile:
Is there some way that I can fetch the current config of an app to debug if it has something different than I think currently running?

2

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