Other reasons: one could run multiple locators, and designate one for
client connection and other for jmx.
-Anil.
On Fri, Feb 24, 2017 at 2:20 PM, Galen M O'Sullivan
wrote:
> I can see that you might want to configure them separately, so it's good to
> have both options.
>
> If I was to design
I can see that you might want to configure them separately, so it's good to
have both options.
If I was to design this again, I think I would have the JMX address etc.
default to the same as the bind address, but as it is that would break
backwards compatibility.
-Galen
On Fri, Feb 24, 2017 at 1
I believe they need to be separate, which helps to provide better control
over application connection (who can connect to what)...
They should all have default bind address, right?
-Anil.
On Fri, Feb 24, 2017 at 12:57 PM, Kevin Duling wrote:
> When starting a locator, gfsh has the --bind-addr
When starting a locator, gfsh has the --bind-address option to tie to a
particular NIC. E.g.,
start locator --name=loc-sec
--security-properties-file=./security.properties
--classpath=/Users/kduling/gfsh-security --bind-address=localhost
This address is the one the server uses to connect with.
