> > 1. The bash -x -e command in vagrant/bootstrap.sh didn't work. I had to > remove the -e switch. >
I had this issue as well. The simplest fix is to remove the switches and set the options near the top of the script: set -e set -x 2. conf/yarn-site.xml forces YARN to bind to 127.0.0.1. This means that > 192.168.0.20:8088/cluster/apps doesn't work. Eliminating the > yarn.resourcemanager.hostname property fixed this. > > Once I did that, I still couldn't contact 192.168.0.20 from my host > machine. I suspect there's some configuration that needs to be set (or > removed) to make this work. The port configured in the Vagrantfile is 192.168.80.20, which may be part of the problem. I haven't been able to contact the resource manager in Vagrant either; the node manager is visible and the CLI works, though, so I haven't had the impetus to dig any deeper. > Given that we don't have any owner for this code right now, I'm going to > remove it. > That's too bad; despite the issues, I found the Vagrant setup very useful while bootstrapping myself on Samza recently. Do you have anything in mind as a replacement?
