We don't want to artificially limit the number of servers that start, as that somewhat defeats the purpose of moving the application to scalr. Nor do we want a huge army of idle server instances to start because one of the instances is busy running a backend script, even if they do terminate once the backend script is complete. Do you see my dilemma here?
How do other people handle issues like this? I guess I could build an instance that does nothing but start-up, run a cron script, and then terminate and launch it from my mysql instance cron script. Are there any other ways? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
