Thanks for the reply but the farm role was also deleted and now we cant change auto scaling settings.
Based on your solution, is deleting the only way of stopping the instances to spin up? If I clone the farm and delete the unstable farm, will my problem persist ? On Tue, Jul 26, 2016 at 10:03 PM, Marc O'Brien <[email protected]> wrote: > Hi Kishor, > > After losing connectivity to the instance, Scalr's desired state engine > will attempt to spin up a replacement based on your autoscaling settings. > Manually terminating the new server on an active Farm will cause the same > process to repeat. If you terminate the farm, or decrease the max instance > count in the Farm Role Autoscaling, does this issue persist? > > Many thanks, > Wm. Marc O'Brien > Scalr Technical Support > > > On Tuesday, July 26, 2016 at 6:02:55 AM UTC-6, Kishor Ramanan wrote: >> >> We accidentally terminated a server that was created in scalr from AWS >> console. >> >> Scalr was spinning up the new instances/server for the deleted server. >> >> Removed role from Sclar still new server spins up automatically and old >> servers get teminated. >> >> New servers are not listed in orphan servers too. >> >> Any help on how to solve the issue? >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "scalr-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/scalr-discuss/HtQCW6B1gpo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- *Warm Regards,Kishore* -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
