Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
SPARK stuck in maintenance if benchmarks can't be installed #59
Comments
erik78se
commented
Jun 22, 2017
•
|
NOTE: I managed to get out of the error by setting the configuration:
Then the installation completes and spark enters a "active" state. Even if this is a workaround, the stuck "maintenance" status gives very little information of what's gone wrong. At that point SPARK is not usable either which effectively leaves the installation broken. |
|
Here are some logs from @erik78se Deployment matrix of Spark: https://pastebin.com/bqWKGvZE |
kwmonroe
self-assigned this
Jun 26, 2017
kwmonroe
added
bug
enhancement
labels
Jun 26, 2017
|
@erik78se Spark-Bench is now optional and no longer installed by default. This went in with: https://issues.apache.org/jira/browse/BIGTOP-2834 spark-51 and above contain this fix: Please let me know if you see any other issues related to spark deployment in a restricted network. Thanks! |
erik78se commentedJun 22, 2017
•
Edited 1 time
-
erik78se
Jun 22, 2017
What I try to do: I was trying to showcase a clean installation of hadoop-spark. Defaults on everything.
We have a proxy, but thats taken care of on the model level as such (servernames replaced below):
juju add-model scania-hadoop-spark --config http-proxy=http://ourinternalproxyserver:8080 --config https-proxy=http://ourinternalproxyserver:8080 --config no-proxy=127.0.0.1This is how I installed the bundle:
juju deploy cs:bundle/hadoop-spark-37Everything installs OK up until when it tries so start/install spark. Then it gets stuck.
SPARK ends up in a "maintenance" status
"juju status" gives...
I would expect it to fail into an "error" state here with some useful output telling me what went wrong.
I have concluded with help from "kjackal" in #juju at freenode IRC that its related to when its not possible to download (proxy!) the benchmarks for spark from AWS s3 buckets, the installation never reaches an error state, but instead gets stuck in "maintenance".