[
https://issues.apache.org/jira/browse/WHIRR-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189152#comment-13189152
]
Andrei Savu commented on WHIRR-482:
-----------------------------------
How about having some sort of locking mechanism that prevents Whirr from
starting multiple clusters with the same name? Would that solve the problem for
you?
> destroy-cluster in EC2 terminates any instance belonging to the cluster's
> security group, even if it's not a member of the cluster
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WHIRR-482
> URL: https://issues.apache.org/jira/browse/WHIRR-482
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Evan Pollan
>
> I had three different whirr-created clusters running in EC2, 2 of which
> shared the same cluster name (and, thus, the same security group). They were
> all created from different machines -- i.e. the ~/.whirr/<cluster>/instances
> files were all on different instances. I invoked destroy-cluster from one of
> the "initiating" machines that had created one of the two identically named
> clusters, and the destruction process terminated all of the instances in the
> cluster "owned" by the machine running the destroy-cluster command, as well
> as all of the instances of the other cluster sharing that name.
> Since whirr writes an inventory of all the instances it creates to
> ~/.whirr/<cluster>/instances, shouldn't it use that manifest to drive it's
> instance termination behavior?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
