-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.10 #449
Comments
The current blocker is that when the staging server is up and running, livy doesn't respond to any attempts at contact. Working on this with ops. |
Livy was having an issue with conflicting jar files for jetty. It's possible that fixing that fixes the issue. I tried to deploy to a fresh ubuntu VM from scratch and have been running into all sorts of other problems. There's a python3/python2 issue... |
Okay! I think I have a working staging deployment! The final issue was that Livy was trying to reach Spark on an address that was equivalent to localhost but that didn't resolve to localhost. Adding the addresses it was using to the /etc/hosts file fixed the problem. The key error here was: |
Ah-ha! Good find. |
Need to get a staging server up and running. Need to work through a full workflow on the staging server. Need to fix any bugs discovered.
The text was updated successfully, but these errors were encountered: