Also, don't forget that you can start a server in a 'wait for locator' mode
(I forget the actual option) which should be distinguished from an actual
'orphaned' instance.
--Jens
On Wed, Apr 5, 2017 at 3:54 PM, Michael Stolz wrote:
> I think the current behavior is probably left over from the mu
I think the current behavior is probably left over from the multicast
member discovery days, which are...thankfully...behind us.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Wed, Apr 5, 2017 at 6:53 PM, Michael Stolz wrote:
> Anyway, at the very least it
Anyway, at the very least it's an unusual configuration, so it would be
best if it required some explicit option to start server to say "Yes I know
what I'm doing...I really want a server that has no peers and no locator."
Without that explicit acknowledgement it should just fail and report the
re
I disagree
+1 you can use stop/status by pointing at the directory where the server
is logging.
-1 You cannot connect to the server and issue the command "create
region" or at the simplest "list members".
The GFSH/management behavior should exactly the same as what one would
have when
"--start-locator=" was originally present on "start server" but was
commented out for some reason. You can find the lines in CliStrings.java:
// public static final String START_SERVER__START_LOCATOR = "start-locator";
// public static final String START_SERVER__START_LOCATOR__HELP =
// "To start
But you can interact with it...
1) You can issue "stop server --dir=server1" which will stop it
2) You can issue "status server --dir=server1" which will show the status
for it
3) You can attach with JConsole and manipulate the MBeans. If the MBeans
have operations to create something you can in
My apologies,
"you" should not be interpreted as personal.
I'm highlighting that a server can be created without any configuration,
which allows for an orphan server. A solution should be found for
that either through failing or starting a means that can correctly
administer the server.
Udo,
I was commenting on the statement:
>> Current Geode allows a user to start a server without being linked to a
Locator.
Not specifically starting server with gfsh...
-Anil.
On Wed, Apr 5, 2017 at 3:18 PM, Udo Kohlmeyer wrote:
> Once again..
>
> you missing the point... starting a s
+1 to add a "--start-locator=" option for starting an embedded locator.
However, I can easily see a user starting two servers and expecting to form
a distributed system, but if we start the embedded locator by default, they
won't.
So, I think we should prevent the server from starting up, but give
Once again..
you missing the point... starting a server with "start server
--name=server1" without a locator or cache.xml or jmx-manager
you have created a useless server which you cannot interact with We
need to avoid that...
All the other discussions of how we can start an embe
You can still control a lone server with GFSH. And if you configure it up
front, then you can still have Regions for a Client to use.
$ start server --name=server1 --cache-xml-file=mycachefile.xml
$ stop server --dir=server1
You could also start a JMX Manager in the server or an embedded Locat
One could create data model using cache.xml or embedded
application/api...The server/node could be used as front-end cache for
database to handle peek loads (or streamed data)Client application can
connect to the server and register interest, execute queries, function
-Anil.
On Wed, Apr
Thanks Jinmei! You are right. I missed that.
Thanks,
Jianxia
On Wed, Apr 5, 2017 at 12:24 PM, Jinmei Liao wrote:
> for your #1, there is a --properties-file option when you do "start
> server".
>
> On Wed, Apr 5, 2017 at 12:20 PM, Jianxia Chen wrote:
>
> > Thank you William!
> >
> > I tried wi
for your #1, there is a --properties-file option when you do "start server".
On Wed, Apr 5, 2017 at 12:20 PM, Jianxia Chen wrote:
> Thank you William!
>
> I tried with it. It works. But there is something tricky in order to start
> the embedded locator.
>
> 1) the gemfire.properties file has to
Thank you William!
I tried with it. It works. But there is something tricky in order to start
the embedded locator.
1) the gemfire.properties file has to be in the right place, either in the
server directory or home directory. Looks like this is not documented.
I was trying to specify the propert
That could be another option that could be pursued...
On 4/5/17 12:05, Michael Stolz wrote:
Actually, the server KNOWS it is all by itself, and since that puts into an
unusable state, why not just default to starting an embedded locator on the
default port? Instant single-node GemFire.
--
Mike
Actually, the server KNOWS it is all by itself, and since that puts into an
unusable state, why not just default to starting an embedded locator on the
default port? Instant single-node GemFire.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Wed, Apr 5, 2017
We should add a "--start-locator=" option to the gfsh start server command
with the same semantics as the start-locator property
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Wed, Apr 5, 2017 at 2:03 PM, William Markito Oliveira <
william.mark...@gmail.com>
@Anil,
I agree... quick start to evaluate the product... "start server
--name=server1" is the simplest way to start a server... BUT there are
no regions or anything ... So we really only have a GemFire process that
does not allow you to do anything with it... except connect to it from a
clien
Jianxia, you can set the property "start-locator" in gemfire.properties as
below... So the server then will have an embedded locator.
http://geode.apache.org/docs/guide/11/reference/topics/gemfire_properties.html
start-locator If set, automatically starts a locator in the current process
when the
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=server
>> 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).
Agree with Darrel, for someone who is evaluating the product, it helps to
build quick applica
Hi Darrel,
How to configure a colocated locator in the same server process? Just
curious. What I understand is that the locator is in its own process.
Thanks,
Jianxia
On Wed, Apr 5, 2017 at 10:36 AM, Darrel Schneider
wrote:
> I like the idea of servers failing to start if no locator exists.
>
I'd like the server to refuse to start from gfsh if it can't reach a
locator.
That seems like exactly the correct behavior.
If you want to run a single node system for development, embedding a
locator makes sense.
Funny thing is, I don't know how to do that. Probably want an example for
that somew
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 th
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
wrote:
> Hey there,
>
> Current Geode allows a user to start a server without being linked to a
> Locator. Which in itself is not
26 matches
Mail list logo
