My current application is designed for a single server configuration. It uses a cron script to call a php file that does a nightly batch process that takes as long as an hour or two. It is run as a low priority task so it doesn't incapacitate my system.
With scalr, I've been planning to set up the cron script on the mysql master and submit the request to only one app server. What I'm wondering is how that would be interpreted and handled by ngix on the www server. Assuming that one app instance gets a very processing intensive request, is the load balancer smart enough to launch one additional instance, and then realize that launching additional instances isn't necessary? Will the www server then route traffic to the server that is under-loaded and let the script server be while it finishes? Id' rather keep it as a single call to a single server than to figure out a way to load distribute it. I'm worried that scalr would keep launching instances to try to offload the swamped server even though it is swamped from a single request and not a traffic overload. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
