Hello Scalr Team Any hints / answers on this? Depending on your answer I will need to work on a solution for this. Appreciate your support
Cheers Srini On Tuesday, March 27, 2012 2:28:48 PM UTC+5:30, Srini wrote: > > I need to add this (critical) piece of info: My app runs on JBoss on a > different port ie. 8080. So ELB is set to check for health on 8080, > whereas I guess Scalr is checking port 80? Would that mean I need to > custom script this? > > Srini > > *From:* Srinivasan Subramanian > *Sent:* Tuesday, March 27, 2012 12:10 PM > *To:* [email protected] > *Subject:* Bug ? ELB and replacing unhealthy servers > > 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 view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/9QOAYgkCWVQJ. 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.
