Hi Brandon, This is expected behavior as Scalr implements a Replace vs a Repair methodology to resource management. You may wish to merge "scalr.openstack.action_on_missing_server = ignore" in to your scalr-server.rb <https://scalr-wiki.atlassian.net/wiki/display/docs/Advanced+Configuration> to prevent Scalr from terminating instances that are marked as "Missing" but there is not currently a method to completely prevent termination of resources that enter an "Error" state. This is intentional, but we do understand your perspective/situation and have considered this previously. We are exploring possible changes to this behavior in future versions of Enterprise Scalr, but this is currently a fundamental behavior of our Desired State Engine and is not something that can be disabled
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Monday, December 5, 2016 at 8:19:38 AM UTC-7, Brandon Newport wrote: > > We are using this version of Scalr, Version 5.11.22. > > On Monday, December 5, 2016 at 9:18:37 AM UTC-6, Brandon Newport wrote: >> >> Is there a way to disable the automatic termination of an Instance with >> Scaling function in the Farm Role settings. >> >> We currently have a Community version of Scalr deployed, and connected to >> OpenStack. By default when an instance goes into ERROR state in >> openstack. Scalr will terminate the existing instance and deploy a new >> one. Is there a way to disable this or ignore the instance in error state? >> We have tested the manual Scaling, but it will still terminate the >> instance and wait for you to redeploy the new instance. >> >> We are gradually working our way to using scaling the way it is designed >> but we are just not there yet. >> >> Any help here would be appreciated. >> >> Brandon >> > -- 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.
