I tried to totally terminate the app role and www roles on my farm which I could not do (this means changing min instances to 0 which is not allowed). What actually happened eventually was that an app server entered into a reboot cycle which caused it to keep terminating and restarting for the whole weekend.
Why was that happening? I can understand scalr starting a new instance to compensate on the min instances number that was 1...but why was it terminating over and over again. Naturally this created an excess charge with AWS due to the fact that a new instance was generated (it was probably not just a reboot). On Dec 18, 7:55 pm, Alex Kovalyov <[email protected]> wrote: > I think Scalr should offer you to decrease MinInstances for corresponding > role when you terminate instances. > You can decrease it by hands anyway - to prevent Scalr from launching > replacements. > > On 18.12.08 19:40, "afishler" <[email protected]> wrote: > > > > > By specifically terminating several instances? > > > Seems like they keep starting up as new instances....Is my only option > > removing them from the farm? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
