Luke, Thanks for your quick reply. I will change /etc/host files and give a try.
It would be great help if you share start locator and start server(s) commands, I am not sure after changing /etc/host file, do i need to use *--bind-address, --hostname-for-clients* options..? and if so what should be its value, internal IP or public IP? so external Java client/gfsh can connect to it. -Upasana. On Mon, Jul 23, 2018 at 3:16 AM, Luke Shannon <[email protected]> wrote: > You need to set the /etc/host files to have the private IP, public IP and > Hostname of all the members in the cluster. See the 'remote' section of > this ReadMe: > https://github.com/lshannon/geode-aws-deployment-scripts/ > blob/master/README.md > > On Sun, Jul 22, 2018, 3:33 PM Upasana Rangwani, <[email protected]> > wrote: > >> Hello, >> >> I am new to Geode and exploring K-V NoSQL to use it for a caching layer >> for out product. >> >> I have setup 2 nodes Geode cluster in GCP and trying to connect it >> programatically (Java client) from my local laptop but having a following >> error, >> >> >> Exception in thread "main" >> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to >> connect to any locators in the list [LocatorAddress >> [socketInetAddress=71.251.200.35.bc.googleusercontent.com/35.200.251.71:10334, >> hostname=35.200.251.71, isIpString=true]] >> at >> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:169) >> at >> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:235) >> >> Geode cluster is formed using internal IPs and i am trying to connect >> locator using public IP of the node (35.200.251.71). I have also tried >> --bind-address and --hostname-for-clients options while starting >> servers/locator, but not able to connect. >> >> Can anyone guide how can i connect (Java client/ gfsh) to a cluster setup >> in cloud platform (GCP, AWS)..? >> >> -Upasana. >> >
