Scheduled Machine not starting -- insufficient memory

Questions / Help
2

Hi!

This means the machine was on a host that didn’t have enough memory available when the scheduled task was scheduled to start.

Generally the way around this is to have multiple machines (they get spread around different hosts). In your case, since it’s a CRON-like behavior, you’ll likely want to do 2 things:

  1. Spin up at least 2 machines
  2. Add a “locking” mechanism is only one machine runs the actual work (assuming that’s what is appropriate for your situation).

This is often done with Redis. At one point we provided Consul for locking like this, I have to check to see if that’s available on our latest apps platform.