Just an update: Changing the cron period for the Poller cronjob to 4 mins solved the multiple-instance-launch issue (finally).
However, I'm unsure what is causing the delay. Placing timing around the EC2 call to RunInstances shows that is only taking a sec or two. Some other interesting observations that may be relevant: 1. When I click the Launch menu option on the roles page to launch a new instance, it takes a long time for the page to refresh. During that time, if I refresh another page (different browser tab in the same browser) showing the system logs, it too takes a long time to refresh and eventually refreshed about when the roles page refreshes. 2. The informational message about the instance being launched (with a green tick) is rendered *on the wrong browser page* (!). That is, if I refresh the page showing the system logs while the roles page hasn't refreshed from requesting a new instance, the message about a new instance being successfully launched appears on the logs page and no message appears on the roles page (!). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
