[jira] [Updated] (SPARK-13317) SPARK_LOCAL_IP does not bind to public IP on Slaves
[ https://issues.apache.org/jira/browse/SPARK-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-13317: - Labels: bulk-closed (was: ) > SPARK_LOCAL_IP does not bind to public IP on Slaves > --- > > Key: SPARK-13317 > URL: https://issues.apache.org/jira/browse/SPARK-13317 > Project: Spark > Issue Type: Bug > Components: Deploy, EC2 > Environment: Linux EC2, different VPC >Reporter: Christopher Bourez >Priority: Minor > Labels: bulk-closed > > SPARK_LOCAL_IP does not bind to the provided IP on slaves. > When launching a job or a spark-shell from a second network, the returned IP > for the slave is still the first IP of the slave. > So the job fails with the message : > Initial job has not accepted any resources; check your cluster UI to ensure > that workers are registered and have sufficient resources > It is not a question of resources but the driver which cannot connect to the > slave given the wrong IP. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-13317) SPARK_LOCAL_IP does not bind to public IP on Slaves
[ https://issues.apache.org/jira/browse/SPARK-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-13317: -- Priority: Minor (was: Major) Component/s: EC2 Deploy Summary: SPARK_LOCAL_IP does not bind to public IP on Slaves (was: SPARK_LOCAL_IP does not bind on Slaves) > SPARK_LOCAL_IP does not bind to public IP on Slaves > --- > > Key: SPARK-13317 > URL: https://issues.apache.org/jira/browse/SPARK-13317 > Project: Spark > Issue Type: Bug > Components: Deploy, EC2 > Environment: Linux EC2, different VPC >Reporter: Christopher Bourez >Priority: Minor > > SPARK_LOCAL_IP does not bind to the provided IP on slaves. > When launching a job or a spark-shell from a second network, the returned IP > for the slave is still the first IP of the slave. > So the job fails with the message : > Initial job has not accepted any resources; check your cluster UI to ensure > that workers are registered and have sufficient resources > It is not a question of resources but the driver which cannot connect to the > slave given the wrong IP. -- 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
