[
https://issues.apache.org/jira/browse/STRATOS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037297#comment-14037297
]
Reka Thirunavukkarasu commented on STRATOS-677:
-----------------------------------------------
Thanks for pointing out Cris. This is also similar issue. I have also discussed
on a similar issue as you faced in here:
http://mail-archives.apache.org/mod_mbox/stratos-dev/201403.mbox/%3CCAFhGutJK3b-bL-oRgoGbVxGpvatV=gvizes7qz5kdew1ohp...@mail.gmail.com%3E
+1. We need to fix this according to the jira (STRATOS-658) that you have
created as well as with a proper rollback mechanism to revert back the already
created unhealthy instances.
> Instances are getting spawn when unsubscribing
> ----------------------------------------------
>
> Key: STRATOS-677
> URL: https://issues.apache.org/jira/browse/STRATOS-677
> Project: Stratos
> Issue Type: Bug
> Components: Autoscaler, Cloud Controller, Eventing
> Affects Versions: 4.0.0
> Reporter: Reka Thirunavukkarasu
> Assignee: Reka Thirunavukkarasu
> Fix For: 4.1.0
>
>
> Even after unsubscribing from a cartridge also, instances are getting
> spawned. The reason for this is, while the CC terminates instances, if the
> minimum rule executed in AS side, then AS will request to spin a new
> instances as it is below the minimum count.
> In order to make AS aware of the unsubscription, we need to introduce another
> state to cluster saying CLUSTER_IN_MAINTENANCE. So that once all the
> instances are terminated, cluster can be removed as well as AS can pause the
> cluster monitor when it is in maintenance mode. Even this state can be useful
> when applying patches or upgrading the cluster.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
