I use the ELB (instead of the nginx role) for load balancing. When the instance is marked unhealthy on the ELB by AWS, Scalr is not detecting this and creating a new instance. Instead ELB indicates its out of service and Scalr is just running the old instance.
Is this a bug or some setup issue in my landscape? If the unhealthy instance is not detected and a new instance recreated, ELB would turn out to be useless right? Cheers Srini -- 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.
