|| at Oct 19, 2009 at 3:52 pm
Sorry to hear that all your EC2 instances were terminated. Needless to
say, this should certainly not happen.
The scripts are a Python rewrite (see HADOOP-6108) of the bash ones so
HADOOP-1504 is not applicable, but the behaviour should be the same:
the terminate-cluster command lists the instances that it will
terminate, and prompts for confirmation that they should be
terminated. Is it listing instances that are not in the cluster? I
have used this script a lot and it has never terminated any instances
that are not in the cluster.
What are the names of the security groups that the instances are in
(both those in the cluster, and those outside the cluster that are
On Mon, Oct 19, 2009 at 4:41 PM, Mark Stetzer wrote:
While running the (latest as of Friday) Cloudera-created EC2 scripts,
I noticed that running the terminate-cluster script kills ALL of your
EC2 nodes, not just those associated with the cluster. This has been
documented before in HADOOP-1504
(http://issues.apache.org/jira/browse/HADOOP-1504), and a fix was
integrated way back on June 21, 2007. My questions are:
1) Is anyone else seeing this? I can reproduce this behavior consistently.
2) Is this a regression in the common code, a problem with the
Cloudera scripts, or just user error on my part?
Just trying to get to the bottom of this so no one else has to see all
of their EC2 instances die accidentally :(