Hi, it seems that there is an implicit restart policy triggering restart of my app’s instances very frequently. I currently have the following scale status:
VM Resources for sync-server VM Size: dedicated-cpu-1x VM Memory: 2 GB Count: 15 Max Per Region: Not set
this is my fly-production.toml’s services section:
[[services]] http_checks =  internal_port = 8080 processes = ["app"] protocol = "tcp" script_checks =  [services.concurrency] hard_limit = 200 soft_limit = 170 type = "connections" [[services.ports]] force_https = true handlers = ["http"] port = 80 [[services.ports]] handlers = ["tls", "http"] port = 443 [[services.tcp_checks]] grace_period = "5s" interval = "30s" restart_limit = 0 timeout = "10s"
vm memory is not an issue (<10% at all times). This app is very slow (currently working on an update) so I guess some sort of http/tcp check might be triggering restarts.
What I see happening is that fly restarts the instance (not intended), and when it reaches a certain amount of restarts (some stopped at 4, other at 9), it kills the instance and provides a fresh one. This happens for all instances, all the time, and eventually fly stops providing fresh instances, reaching a point where I see the 503 error: “no instances to route to”.