Closed antmoth closed 4 years ago
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:
19/08/19 11:21:25 INFO utils.LineBufferedStream: 2019-08-19 11:21:25 WARN RSCConf:146 - Your hostname, [redacted], resolves to a loopback address, but we couldn't find any external IP address!
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.