Re: [DISCUSS] what region types to support in the new management rest api

Maybe to clarify what I said before (which was certainly unclear ), I am not saying we only allow users to create limited set of types of region, we COULD still support all of them, but we should not limit ourselves to the current ways of doing things. Currently, a flat model of region configuratio

Re: [DISCUSS] what region types to support in the new management rest api

Yes it is common for 0,1 and 2. 3 enters into gray space of is the cost of redundancy worth it. So voting for exposing the number of copies to be the same as Apache Geode Java API. Charlie On Tue, Aug 20, 2019 at 11:38 AM Darrel Schneider wrote: > The shortcuts support partitioned regions wi

Re: [DISCUSS] what region types to support in the new management rest api

And if there the old way of specifying types/shortcuts was somehow counter-intuitive, 'cause I did from time to time, hearing things like "I wish we did things differently", this is our chance of correcting it. On Tue, Aug 20, 2019 at 6:47 PM Jacob Barrett wrote: > If you code it you have to tes

Re: [DISCUSS] what region types to support in the new management rest api

If you code it you have to test it. An all or nothing approach will take longer to deliver any value. Breaking it into a priority set and committing the sets gives immediate value. > On Aug 20, 2019, at 6:12 PM, Michael Stolz wrote: > > I'm not at all sure why supporting the current set is mo

Re: [DISCUSS] what region types to support in the new management rest api

I'm not at all sure why supporting the current set is more work than a subset. Are we planning to fix issues in the current implementation in the new API rather than the underlying (still needed) existing API? How is that a good idea? -- Mike Stolz Principal Engineer, Pivotal Cloud Cache Mobile:

Re: [DISCUSS] what region types to support in the new management rest api

My vote is for supporting all the region type currently supported. As mike was pointing, we have seen usecases where different regions are used for specific application needs. On Tue, Aug 20, 2019 at 5:09 PM Darrel Schneider wrote: > gfsh create region currently does not support "distributed-n

Re: [DISCUSS] what region types to support in the new management rest api

gfsh create region currently does not support "distributed-no-ack" nor "global". I did not find in jira a feature request for gfsh to support these. So I think it would be safe for the Geode Management REST API to also not support those scopes. On Tue, Aug 20, 2019 at 12:10 PM Kirk Lund wrote:

Need help: Jetty dunit tests blocking creation of geode-log4j

Does anyone know how to debug geode-assembly Jetty dunit tests that fail to launch modify_war? It passes 100% locally in intellij and with gradle cli. It only fails in concourse PR precheckin. Right now, this is the last thing blocking me from submitting a non-draft PR to move all log4j-core code

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

Thanks for all the great feedback and comments. *API Name change:* *Suggestion: *startPaused*,*setManualStart*, *startWithEventDispatcherPaused*?, createPaused()* *Start/Stop behavior:* *- Manual start has caused a lot of trouble over the years.- Explain starting AEQ in a paused state is differ

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

FTR, I am not opposed to *Naba's* idea either. +1 I kind of like the idea of having a global, cache-wide call that can coordinate the background initialization/processing of all other Geode objects that have lifecycle processes starting in the background (e.g. Gateways, AEQs, etc). On Tue, A

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

If we need to add pause/resume processing to Cache, I suggest adding setAutostart(boolean) to CacheFactory and start() to Cache to do something like this: Cache cache = new CacheFactory() *.setAutostart(false)* .create(); cache.createRegionFactory(...)... cache.createAsyncEventQueu

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

After talking with *Alexander* this morning (and taking *Mike's* concerns into consideration), and to not adversely affect users/customers today, I think... 1). AEQ's can (should) have a configuration setting to "manually" start the queue's background processor (i.e. Thread) to begin processing (e

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

Hi Anil, Will it be possible to explain to the community how the starting AEQ in a paused state is different from creating gateway senders with manual start set to true. It may be of concern as 'manual start' for gateways is a deprecated. Just thinking out loud, will it be more feasible if we c

[DISCUSS] Add a public API to add endpoints to Geode's HTTP server

I’ve drafted a proposal to add a public API to add endpoints to Geode’s HTTP server. https://cwiki.apache.org/confluence/display/GEODE/%5BDraft%5D+Public+API+to+Add+Endpoints+to+Geode+HTTP+Server

Re: [DISCUSS] what region types to support in the new management rest api

Here's my 2cents: The Geode Management REST API should definitely support "group" such that creation of a region may target zero, one, or more groups. On Tue, Aug 20, 2019 at 10:45 AM Darrel Schneider wrote: > Is "group" support on the PCC roadmap or is the plan for the members of a > cluster to

Re: [DISCUSS] what region types to support in the new management rest api

By far the most common region "scope" is distributed-ack. We think LOCAL scope is hardly ever used. Partitioned regions ignore the scope and automatically use "distributed-ack". Should the default scope of "distributed-no-ack" be supported by the rest management api for replicates? Should the scop

Re: [DISCUSS] what region types to support in the new management rest api

The shortcuts support partitioned regions with 0 and 1 redundant copies. Is redundancies greater than 1 common enough for the rest management api to support it? On Tue, Aug 20, 2019 at 11:27 AM Jacob Barrett wrote: > +1 to Alexander’s statement. > > Also, initial revisions need not be feature pa

Re: [DISCUSS] what region types to support in the new management rest api

+1 to Alexander’s statement. Also, initial revisions need not be feature parity. For us on the common use cases. It’s sounds like an advanced use case to have proxy regions on the server so focus on the common partitioned and replicated first for the initial release. -jake > On Aug 20, 2019,

Re: [DISCUSS] what region types to support in the new management rest api

Hey folks, I want to make sure that any other's product's roadmaps have no impact on any decisions we make about Apache Geode. Thanks! On Tue, Aug 20, 2019 at 10:45 AM Darrel Schneider wrote: > Is "group" support on the PCC roadmap or is the plan for the members of a > cluster to always be unif

Re: [DISCUSS] what region types to support in the new management rest api

Is "group" support on the PCC roadmap or is the plan for the members of a cluster to always be uniform? On Tue, Aug 20, 2019 at 9:56 AM Jinmei Liao wrote: > So, sound like we still need to support *PROXY types. It's OK to drop > support for LOCAL* region types in management rest API? > > Also, r

Re: [DISCUSS] what region types to support in the new management rest api

So, sound like we still need to support *PROXY types. It's OK to drop support for LOCAL* region types in management rest API? Also, regarding existing region shortcuts, we are also experimenting using different object types to represent different types of region, for example, redundantCopies prope

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

Manual start has caused a lot of trouble over the years. We should definitely circle back on those issues before traveling very far down this road. -- Mike Stolz Principal Engineer, Pivotal Cloud Cache Mobile: +1-631-835-4771 On Tue, Aug 20, 2019 at 11:56 AM Juan José Ramos wrote: > Hello Ani

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

+1 to Juan's comment. I wonder if it would make sense just to have a variation on the existing create() method. Either have a createPaused() method or add an overload for create() that takes a startPaused boolean. That will really drive home that the AsyncEventQueue will be created in a paused st

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

Hello Anil, +1 for the proposed solution. I'd change the method name from *pauseEventDispatchToListener* to something more meaningful and understandable for our users, maybe *startPaused*?, *setManualStart* (as we currently have for the *GatewaySenderFactory*)?, *startWithEventDispatcherPaused*?.

Re: [DISCUSS] what region types to support in the new management rest api

Currently, when deployed to the cloud (aka PCC) there is no ability for a user to group members thus it is also not possible to create regions (via gfsh at least) that are separated by groups. Typically one would create a PROXY region against one group and the PARTITION region against another group

Re: [DISCUSS] what region types to support in the new management rest api

I know that lots of folks use PROXY regions on the server side to host logic associated with the region, but I think they always do that in conjunction with server groups so that the proxy is on some of the server and the same region containing data is on others. Given the way cache.xml works they

Rat check reporting error in travis-ci for geode-native

Hi, I sent a PR for the geode-native repo and the travis-ci is reporting a Rat error on the following file: ./packer/windows/install-doxygen.ps1 The reason is that the copyright header is not included in it. I could add it in my PR but I guess it would be more convenient if this is fixed on a