I think an embedded server makes sense. No locator required, UNLESS you
want to form a cluster and then I think you need a locator. (haven't
tried this without multicast)
Shutting down a server with --pid or --dir works. BUT... One cannot
connect to a default server "start server --name=server1". This is a
server that can only be connected to directly from a client, BUT the
client cannot do any admin (create region, etc)... So in essence when
starting a server without locator or management interfaces (REST,JMX)
enabled, just wastes space and cannot be managed...
I'd like to suggest that if we start an "orphan" server, it either does
not allow it to be started, because it is really just sitting there
without any management capability OR we detect that no management
interfaces have been configured and start the JMX manager to allow for
management.
--Udo
On 4/5/17 10:36, Darrel Schneider wrote:
I like the idea of servers failing to start if no locator exists.
But does a use case for a server with no locator exist? What about ease of
development?
I could see that it would be easier to start just a single server process
instead of two (locator and server). But for this use case couldn't the
developer just configure a colocated locator in the same server process?
This would have the benefit of the clients during development and
production using a locator consistently.
Is it true that the server with no locator will never have any peer members
in its cluster?
Clients can still connect to this singleton server by being configured with
the server host and port instead of the locator.
On Wed, Apr 5, 2017 at 10:24 AM, Jinmei Liao <jil...@pivotal.io> wrote:
Without connecting to the server, I think you can still stop it by
specifying --pid or --dir in "stop server" command.
On Wed, Apr 5, 2017 at 10:15 AM, Udo Kohlmeyer <ukohlme...@pivotal.io>
wrote:
Hey there,
Current Geode allows a user to start a server without being linked to a
Locator. Which in itself is not incorrect, but once started there is no
way
to connect to that server to manage it.
I know that we have taken an opinionated view that member discovery can
only now happen through a locator and that multicast is an option
anymore.
Can we take the same opinionated view where we either state that unless
your server is connecting to a locator, it cannot be started OR we fix
the
default behavior where we can start a server but cannot connect to it,
and
have to resort to "kill -9" commands to kill the server.
--Udo
--
Cheers
Jinmei
