-
Notifications
You must be signed in to change notification settings - Fork 34
dcos spark not installed #240
Comments
Same problem here. DCOS : 1.10.1 |
In my case this issue seems to be due to a DNS problem. While booting, spark is trying to solve the hostname of the host, and if this entry is neither in the You should be able to check it by connecting to the node hosting the spark docker container via
Any node or master in your cluster should be able to run correctly When installing, DCOS crush the existing configuration existing in We're deploying on AWS, and we're able to solve the issues by adding the Amazon DNS address in the dcos config file :
|
@dprslt's fix works for me as well. Thanks! Which project is responsible for this issue though? DC/OS? |
In fact, i don't thing is really an "issue". It's a configuration issue because the dns or the hosts file is unable to resolve the hostname. The issue is mainly a lack of logging in the DC/OS web view. |
@grohan2002, if you could modify your If $HOSTNAME is set, here's my script for 1. removing the line from sudo sed -i '/'$HOSTNAME'/d' /etc/hosts
export IP=$(hostname -I | awk '{print $1}')
echo $IP' '$HOSTNAME | sudo tee -a /etc/hosts Try it first. |
@hantuzun Thanks a lot for the workaround , however i did input the Amazon DNS in the config.yaml file and rebuilt the DC/OS stack . |
@grohan2002, building DC/OS takes a long time and could fail randomly according to my experience. I'm more cautious on touching DC/OS now. |
I have a dcos 1.10 cluster on centos 7.3, where hdfs has been successfully installed. When I want to install the Spark through the Catalog in the Web UI, meet the same issue as this, which is solved by change the username from
nobody
toroot
. Now, the permission denied issue is gone, but I'm still unable to run Spark with Spark logs showinghere is the option file:
The Spark service is also showing as
Unhealth
in the web UI. When checking fromMarathon
, it saysTask was killed since health check failed. Reason: 502 Bad Gateway
.Any idea how to fix it?
The text was updated successfully, but these errors were encountered: