John, thanks for your answer. I decided to bite the bullet and now build a jar on my windows machine and ship it to the linux machine to execute. It works.
Sorry I did not get back to you before now. Dave On Wed, Feb 4, 2015 at 10:04 AM, John Vines <[email protected]> wrote: > In your cluster, define your machines by the public ip address or a name > that resolves to that address. Then restart. > > I'm willing to bet your slaves file and such says localhost which will > cause the machines to register as localhost instead of the public ip > address. > > Sent from my phone, please pardon the typos and brevity. > On Feb 4, 2015 9:41 AM, "David Patterson" <[email protected]> wrote: > >> I have some java code that works fine when it is running on the same >> (cloud-Ubuntu) machine as a small testbed of data. >> >> If I run the exact same code on a Windows machine it hangs up after the >> following warning: >> >> INFO : Initiating client connection, connectString=10.14.6.104:2181 >> sessionTimeout=30000 >> watcher=org.apache.accumulo.fate.zookeeper.ZooSession$ZooWatcher@1bb75db9 >> INFO : Opening socket connection to server 10.14.6.104/10.14.6.104:2181. >> Will not attempt to authenticate using SASL (unknown error) >> INFO : Socket connection established to 10.14.6.104/10.14.6.104:2181, >> initiating session >> INFO : Session establishment complete on server >> 10.14.6.104/10.14.6.104:2181, sessionid = 0x14b284b3736008e, negotiated >> timeout = 30000 >> WARN : Failed to find an available server in the list of servers: >> [localhost:9997 (120000)] >> >> I'm guessing it has to do with some aspect of the security handshake not >> being implemented and having that matter a lot when trying to process a >> request from a "remote" source. >> >> I have been unsuccessful in finding what is needed and how to fix it. >> >> Any pointers will be appreciated. >> >> Dave P >> >> >
