Thank you, Jens and Ajay - I have it working now On Sun, Oct 13, 2019 at 10:43 AM ajay vasudevan <vasudevan.a...@gmail.com> wrote:
> Hi Jim, > > The following commands would work for you to connect to a local geode > cluster : > > docker run --rm -it --name localhost --hostname localhost -p 8080:8080 -p > 10334:10334 -p 40404:40404 -p 1099:1099 -p 7070:7070 > apachegeode/geode:1.10.0 > > Start locator > ========== > start locator --name=myLocator --hostname-for-clients=localhost > --log-level=config > --J='-Dgemfire.jmx-manager-hostname-for-clients=localhost' > > Start server > ========= > start server --name=myServerOne --locators=localhost[10334] > --server-port=40404 > > Regards, > aj-vas > > On Sat, Oct 12, 2019 at 8:07 PM Jens Deppe <jensde...@apache.org> wrote: > >> Hi James, >> >> Could you clarify this: >> >>> >>> When I try to use the docker image, I get: >>> Exception in thread "main" >>> org.apache.geode.cache.client.NoAvailableServersException >>> >>> >> What are you doing when this happens? Perhaps obvious, but just to be >> clear you do need to keep the docker session running otherwise the started >> geode members will just go away when the gfsh shell exits. >> >> I think the instructions do need to be updated a bit. If you're trying to >> connect to the cluster from your host you should use the following to start >> the locator and server: >> >> start locator --hostname-for-clients=localhost >> --jmx-manager-hostname-for-clients=localhost >> --J=-Djava.rmi.server.hostname=localhost >> start server --hostname-for-clients=localhost >> >> >> Since the started cluster will be using docker non-public IPs (probably >> on a 172.17.0.0/16 subnet) any externally connecting client will not be >> able to connect directly to these addresses, but will need to use the >> localhost proxy ports as exposed by docker. >> >> --Jens >> >
