Scalr spins up new ec2 servers automatically in aws even though the role was removed from Scalr

[Kishor Ramanan]

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?

[Marc O'Brien]

Hi Kishor,

After an instance enters a non-running state, 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

[Kishor]

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 <ma...@scalr.com> 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?

--
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 scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Warm Regards,
Kishore

[Marc O'Brien]

Hi Kishor,

The problem that you are experiencing is not clear.  Once the farm and/or farm role have been deleted or terminated, Scalr should no longer be attempting to create new replacement servers.  To be clear, you have deleted this farm role from a terminated farm and you believe that Scalr is still attempting to spin up new servers related to this?  Screenshots of your experience may be useful to help illustrate your problem.

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

To unsubscribe from this group and all its topics, send an email to scalr-discuss+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Warm Regards,
Kishore

[Marc O'Brien]

From external email:

"Hi Marc,

We have removed the roles and deleted the farm, still the instance continues to spin up.

We don't have auto scaling in AWS, the newly spin up instance still has reference to the old Farm ID

(Inline image 1)

I am not able to delete the instances without replacement getting created. :(

Not sure how Sclar triggers the instances even with no Farm or Roles"