Re: Connecting java client to Accumulo VM

Thanks for the best practice advice wrt accumulo-env.sh. I was using .profile because Hadoop finds it well enough. On Thu, Nov 9, 2017 at 12:04 PM, Josh Elser wrote: > +1 to Christopher's assessment of the JAVA_HOME issue. > > A bit more color if you find it interesting:

Re: Connecting java client to Accumulo VM

+1 to Christopher's assessment of the JAVA_HOME issue. A bit more color if you find it interesting: Accumulo tends to do a bit of SSH'ing in starting up processes (this has gotten better in the 1.8 or 2.0 scripts). As such, it's a best-practice to explicitly set environment variables you need

Re: Connecting java client to Accumulo VM

So, Accumulo TServers publish their hostname from their config into the Accumulo metadata. So, yes, this hostname must be reachable by clients as well, because that's how clients will identify it in the Accumulo metadata. I'm not sure what the deal was with the JAVA_HOME variable. It's probably

Re: Connecting java client to Accumulo VM

All, Muchas gracias for the help. When I had masters/slaves populated with "localhost", 9997 was listening but not remotely. When I had m/s populated with the IP address, 9997 was not listening and the log said JAVA_HOME was not set and that I should set it in accumulo-env.sh. I did that and

Re: Connecting java client to Accumulo VM

Yep should work. would suggest checking the logs at this point to see what’s causing the failure. If it’s not starting up there would be exceptions thrown by the service. On Wed, Nov 8, 2017 at 5:36 PM Geoffry Roberts wrote: > I tried the IP address (a 192 number) but

Re: Connecting java client to Accumulo VM

I tried the IP address (a 192 number) but the same result--no 9997. Using said IP I can access from either the host or from within the guest. So far nothing works in master/slaves except localhost. I gather this is supposed to work correct? On Wed, Nov 8, 2017 at 5:16 PM, Edward Gleeck

Re: Connecting java client to Accumulo VM

You wouldn't want the 0.0.0.0 on your /etc/hosts as this wouldn't be valid. I don't recall exactly which configuration file under $ACCUMULO_CONF_DIR you would want this in as Josh pointed out, but if you were to go the /etc/host route, you want to put the IP address of that interface VM host. for

Re: Connecting java client to Accumulo VM

I gave your suggestion a try. I made an entry in /etc/hosts that resolves to 0.0.0.0 then set that name in master and slaves. (I am running single node for now.). The upshot is port 9997 does not appear as listening at all. If I change back to localhost, then it appears again. My guess is the

Re: Connecting java client to Accumulo VM

Accumulo chooses the network interface to bind given the resolution of the hostname that you provide in the "hosts" files in ACCUMULO_CONF_DIR. If you have "localhost" (the default) still in the files (e.g. masters, slaves), this presumably resolves to 127.0.0.1 which will result in Accumulo

Connecting java client to Accumulo VM

All, I have used Accumulo before, but a few versions ago (1.5.1), maybe something has changed. Also, I've never before run it in a VM. I am running Accumulo from withn a VM and attempting to connect from without. I am getting a complaint regarding port 9997, which, within the VM, is listening