[ https://issues.apache.org/jira/browse/SPARK-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jey Kottalam updated SPARK-4731: -------------------------------- Description: EC2 clusters launched using Spark 1.1.1's `spark-ec2` script with the `-v 1.1.1` flag fail to initialize the master and workers correctly. The `/root/spark` directory contains only the `conf` directory and doesn't have the `bin` and other directories. [~joshrosen] suggested that [spark-ec2 #81](https://github.com/mesos/spark-ec2/pull/81) might have fixed it, but I still see this problem after that was merged. was: EC2 clusters launched using Spark 1.1.1 with the `-v 1.1.1` flag fail to initialize the master and workers correctly. The `/root/spark` directory contains only the `conf` directory and doesn't have the `bin` and other directories. [~joshrosen] suggested that [spark-ec2 #81](https://github.com/mesos/spark-ec2/pull/81) might have fixed it, but I still see this problem after that was merged. > Spark 1.1.1 launches broken EC2 clusters > ---------------------------------------- > > Key: SPARK-4731 > URL: https://issues.apache.org/jira/browse/SPARK-4731 > Project: Spark > Issue Type: Bug > Components: EC2 > Affects Versions: 1.1.1 > Environment: Spark 1.1.1 on MacOS X > Reporter: Jey Kottalam > > EC2 clusters launched using Spark 1.1.1's `spark-ec2` script with the `-v > 1.1.1` flag fail to initialize the master and workers correctly. The > `/root/spark` directory contains only the `conf` directory and doesn't have > the `bin` and other directories. > [~joshrosen] suggested that [spark-ec2 > #81](https://github.com/mesos/spark-ec2/pull/81) might have fixed it, but I > still see this problem after that was merged. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org