Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

Voting summary: +1: 8 0: 0 -1: 0 git cherry-pick -x e148cef9cb63eba283cf86bc490eb280023567ce completed on release/1.11.0. > On Nov 26, 2019, at 1:35 PM, Ivan Godwin wrote: > > +1 > > On Tue, Nov 26, 2019 at 1:31 PM Xiaojian Zhou wrote: > >> +1 >> >> On Tue, Nov 26, 2019 at 12:48 PM Joris

Re: Cache.close is not synchronous?

I added a stack trace to the closing of both GemFireCacheImpl and InternalDistributedSystem and found a difference. The test passes when it's the test thread doing the close: java.lang.Throwable: KIRK GemFireCacheImpl closed 1046056441 at org.apache.geode.internal.cache.GemFireCacheImpl.c

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 1:31 PM Xiaojian Zhou wrote: > +1 > > On Tue, Nov 26, 2019 at 12:48 PM Joris Melchior > wrote: > > > +1 > > > > On Tue, Nov 26, 2019 at 2:41 PM Jason Huynh wrote: > > > > > +1 > > > > > > On Tue, Nov 26, 2019 at 11:34 AM Anilkumar Gingade < > aging...@pivotal.io> > >

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 12:48 PM Joris Melchior wrote: > +1 > > On Tue, Nov 26, 2019 at 2:41 PM Jason Huynh wrote: > > > +1 > > > > On Tue, Nov 26, 2019 at 11:34 AM Anilkumar Gingade > > wrote: > > > > > +1 > > > > > > On Tue, Nov 26, 2019 at 11:32 AM Udo Kohlmeyer wrote: > > > > > > > Thi

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 2:41 PM Jason Huynh wrote: > +1 > > On Tue, Nov 26, 2019 at 11:34 AM Anilkumar Gingade > wrote: > > > +1 > > > > On Tue, Nov 26, 2019 at 11:32 AM Udo Kohlmeyer wrote: > > > > > This is no-brainer > > > > > > *+1* > > > > > > On 11/26/19 11:27 AM, Owen Nichols wrote:

Re: [VOTE] Release candidate for Apache Geode version 1.11.0.RC3.

-1 from native client as well, sorry. RC3 mistakenly picked up an unnecessary commit, and left out the crash fix I needed. If you revert commit 5d012199055a9a7657563727f6e26a406b287fc3 and cherry-pick 55da853760c200c53568fe2e6549c912ec26cc27, "GEODE-7426: Fixes segfault in log message.", native c

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 11:34 AM Anilkumar Gingade wrote: > +1 > > On Tue, Nov 26, 2019 at 11:32 AM Udo Kohlmeyer wrote: > > > This is no-brainer > > > > *+1* > > > > On 11/26/19 11:27 AM, Owen Nichols wrote: > > > I would like to propose bringing “GEODE-7465: Set eventProcessor to > null >

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 11:32 AM Udo Kohlmeyer wrote: > This is no-brainer > > *+1* > > On 11/26/19 11:27 AM, Owen Nichols wrote: > > I would like to propose bringing “GEODE-7465: Set eventProcessor to null > in serial AEQ when it is stopped” into the 1.11 release (necessitating an > RC4). >

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 11:32 AM Udo Kohlmeyer wrote: > This is no-brainer > > *+1* > > On 11/26/19 11:27 AM, Owen Nichols wrote: > > I would like to propose bringing “GEODE-7465: Set eventProcessor to null > in serial AEQ when it is stopped” into the 1.11 release (necessitating an > RC4). >

Re: [VOTE] Release candidate for Apache Geode version 1.11.0.RC3.

-1: Analyzing a hang that looks similar to GEODE-5307: Hang with servers all in waitForPrimaryMember and one server in NO_PRIMARY_HOSTING state https://issues.apache.org/jira/browse/GEODE-5307 On Mon, Nov 25, 2019 at 9:13 PM Mark Hanson wrote: > Hello Geode Dev Community, > > This is a release c

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

This is no-brainer *+1* On 11/26/19 11:27 AM, Owen Nichols wrote: I would like to propose bringing “GEODE-7465: Set eventProcessor to null in serial AEQ when it is stopped” into the 1.11 release (necessitating an RC4). Without the fix, a sequence of ordinary gfsh commands will leave the WAN

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

+1 On Tue, Nov 26, 2019 at 11:27 AM Owen Nichols wrote: > I would like to propose bringing “GEODE-7465: Set eventProcessor to null > in serial AEQ when it is stopped” into the 1.11 release (necessitating an > RC4). > > Without the fix, a sequence of ordinary gfsh commands will leave the WAN > ga

[DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

I would like to propose bringing “GEODE-7465: Set eventProcessor to null in serial AEQ when it is stopped” into the 1.11 release (necessitating an RC4). Without the fix, a sequence of ordinary gfsh commands will leave the WAN gateway in an unrecoverable hung state: stop gateway-sender start gate

Re: Cache.close is not synchronous?

Seems like this must be a bug, so I filed https://issues.apache.org/jira/browse/GEODE-7503. I'll look into it... On Mon, Nov 25, 2019 at 3:24 PM Anilkumar Gingade wrote: > Looking at the code, the cache.close() and InternalCacheBuilder.create() > are synchronized on "GemFireCacheImpl.class"'; it

Re: Cache.close is not synchronous?

+1 for fixing. On Tue, Nov 26, 2019 at 6:53 AM Alberto Bustamante Reyes wrote: > +1 for fixing it. > > De: Anilkumar Gingade > Enviado: martes, 26 de noviembre de 2019 0:24 > Para: geode > Asunto: Re: Cache.close is not synchronous? > > Looking at the code, the

Re: Odg: Odg: Restart gateway-receiver

It’s is likely that your firewall is closing idle connections. This is very common for a firewall to drop the state information for a connection that hasn’t seen any traffic in some set period of time. It’s a way for firewalls to reclaim resources for connections that were likely closed on one s

RE: Cache.close is not synchronous?

+1 for fixing it. De: Anilkumar Gingade Enviado: martes, 26 de noviembre de 2019 0:24 Para: geode Asunto: Re: Cache.close is not synchronous? Looking at the code, the cache.close() and InternalCacheBuilder.create() are synchronized on "GemFireCacheImpl.class"'; i

Odg: Odg: Restart gateway-receiver

Thanks a lot @Barry Oglesby! It seems that this closing inactive connection is done by Kubernetes as we run Geode on it. BR, Mario Šalje: Barry Oglesby Poslano: 22. studenog 2019. 22:35 Prima: Mario Kevo Kopija: dev@geode.apache.org

Odg: Proposal of new config property "ssl-server-name-extension"

Hi Sai, The security provider main class is configured through a java security file: -Djava.security.properties=custom-security.file Where we set: security.provider.1=my.security.provider.class The security provider is packaged as a .jar and added to the classpath. The security provider