+1
On 3/1/21, 11:30 PM, "Owen Nichols" wrote:
That sounds a lot better than never expiring them if that does happen, I
think this would be good to include.
On 3/1/21, 2:41 PM, "Mark Hanson" wrote:
I would like to backport GEODE-8958 into previous release branches to
allevia
+1
From: Xiaojian Zhou
Sent: Wednesday, March 3, 2021 9:43 AM
To: dev@geode.apache.org
Subject: Re: [Proposal] Backport GEODE-8958 into 1.14.x, 1.13.x, 1.12.x branches
+1
On 3/1/21, 11:30 PM, "Owen Nichols" wrote:
That sounds a lot better than never expir
+1
On Wed, Mar 3, 2021 at 9:44 AM Darrel Schneider wrote:
> +1
>
> From: Xiaojian Zhou
> Sent: Wednesday, March 3, 2021 9:43 AM
> To: dev@geode.apache.org
> Subject: Re: [Proposal] Backport GEODE-8958 into 1.14.x, 1.13.x, 1.12.x
> branches
>
> +1
>
> On 3/1/21
I would like to backport the fix of GEODE-8671, currently a 1.14 blocker,
to support/1.14, support 1.13 and support/1.12. This would help avoid Pdx
corruption.
Thanks,
Jianxia
+1
On 3/3/21, 10:24 AM, "Jianxia Chen" wrote:
I would like to backport the fix of GEODE-8671, currently a 1.14 blocker,
to support/1.14, support 1.13 and support/1.12. This would help avoid Pdx
corruption.
Thanks,
Jianxia
Hi Mario,
Thanks for discovering this difference in behavior between the geode-native
clients (C++ and .NET) and geode Java client regarding the sync'ing of local
caches after a restore operation.
It looks like geode-native has no tests for the exception type you're seeing:
GF_CACHE_CONCURRENT
This was already added to the 1.14.0 blocker board on Feb 19 so you are free to
backport it anytime, no need for additional proposal. Additionally
support/1.13 and support/1.12 do not have an active Geode release proposal or
release manager so it's fine to bring fixes any time.
On 3/3/21, 11:
Thanks Owen!
On Wed, Mar 3, 2021 at 11:33 AM Owen Nichols wrote:
> This was already added to the 1.14.0 blocker board on Feb 19 so you are
> free to backport it anytime, no need for additional proposal. Additionally
> support/1.13 and support/1.12 do not have an active Geode release proposal
>
+1 to back-port GEODE-8920 fix
On Mon, Mar 1, 2021 at 1:23 PM Owen Nichols wrote:
> Sounds reasonable for same reasons as GEODE-8919. I've added it to 1.14.0
> blocker board.
>
> On 3/1/21, 1:20 PM, "Kamilla Aslami" wrote:
>
> Hi all,
>
> I would like to back-port the fix for GEODE-89
+1
On Wed, Mar 3, 2021 at 9:51 AM Jianxia Chen wrote:
> +1
>
> On Wed, Mar 3, 2021 at 9:44 AM Darrel Schneider wrote:
>
> > +1
> >
> > From: Xiaojian Zhou
> > Sent: Wednesday, March 3, 2021 9:43 AM
> > To: dev@geode.apache.org
> > Subject: Re: [Proposal] Backp
I would like to backport GEODE-8998 to 1.14. If fixes an NPE
that will cause the geode cluster to not be able to do any
cluster messaging if thread monitoring is disabled.
This bug has never been released so it would be nice
keep it that way.
https://issues.apache.org/jira/browse/GEODE-8998
11 matches
Mail list logo
