You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Theodore Vasiloudis (JIRA)" <ji...@apache.org> on 2016/02/02 12:47:39 UTC
[jira] [Updated] (SPARK-13143) EC2 cluster silently not destroyed
for non-default regions
[ https://issues.apache.org/jira/browse/SPARK-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Theodore Vasiloudis updated SPARK-13143:
----------------------------------------
Description:
If you start a cluster in a non-default region using the EC2 scripts and then try to destroy it, you get the message:
{quote}
Terminating master...
Terminating slaves...
{quote}
after which the script terminates with no further info.
This leaves the instances still running without ever informing the user.
The reason this happens is that the destroy action in {{spark_ec2.py}} calls {{get_existing_cluster}} with the {{die_on_error}} argument set to {{False}} for some reason.
I'll submit a PR for this.
was:
If you start a cluster in a non-default region using the EC2 scripts and then try to destroy it, you get the message:
{quote}
Terminating master...
Terminating slaves...
{quote}
after which the script terminates with no further info.
This leaves the instances still running without ever informing the user.
The reason this happens is that the destroy action in `spark_ec2.py` calls `get_existing_cluster` with the `die_on_error` argument set to `False` for some reason.
I'll submit a PR for this.
> EC2 cluster silently not destroyed for non-default regions
> ----------------------------------------------------------
>
> Key: SPARK-13143
> URL: https://issues.apache.org/jira/browse/SPARK-13143
> Project: Spark
> Issue Type: Bug
> Components: EC2
> Affects Versions: 1.5.0
> Reporter: Theodore Vasiloudis
> Priority: Minor
> Labels: trivial
>
> If you start a cluster in a non-default region using the EC2 scripts and then try to destroy it, you get the message:
> {quote}
> Terminating master...
> Terminating slaves...
> {quote}
> after which the script terminates with no further info.
> This leaves the instances still running without ever informing the user.
> The reason this happens is that the destroy action in {{spark_ec2.py}} calls {{get_existing_cluster}} with the {{die_on_error}} argument set to {{False}} for some reason.
> I'll submit a PR for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org