Re: [Proposal] Backport GEODE-8958 into 1.14.x, 1.13.x, 1.12.x branches

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 alleviate a problem with tombstones if timestamps become corrupt for

Re: Cached regions are not synchronized after restore

Hi everyone, After replicating the test with both clients being the Java implementation, I could verify that what @Dan Smith pointed out about the documentation is happening. Every time subscription redundancy is lost, cached entries are erased. This is clearly not ha

[Proposal] Backport GEODE-8958 into 1.14.x, 1.13.x, 1.12.x branches

I would like to backport GEODE-8958 into previous release branches to alleviate a problem with tombstones if timestamps become corrupt for some reason. Thanks, Mark

Re: [PROPOSAL] backport fix for GEODE-8920 to 1.14.0

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-8920 to 1.14.0. It modified debug logging in DirectChannel to make it easier to trace a message. T

[PROPOSAL] backport fix for GEODE-8920 to 1.14.0

Hi all, I would like to back-port the fix for GEODE-8920 to 1.14.0. It modified debug logging in DirectChannel to make it easier to trace a message. This change is low-risk and important for debugging. Thanks, Kamilla

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Since redis effort has been a big theme for 1.14, it makes sense to polish what's there as best as possible for its first release. Thanks for putting together this list, it feels like these are finishing touches and low risk, so I'll add them to the 1.14.0 blocker board. On 3/1/21, 11:57 AM

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

We're actually hoping to get a few things into 1.14 to help make the compatibility with Redis to be useful: Merged to develop: GEODE-8933: Report max memory setting in Geode Redis statistics GEODE-8894: Allow individual deltas to trigger bucket size recalculation GEDOE-8865: Create additional dun

Re: [PROPOSAL] backport fix for GEODE-8919 to 1.14.0

+1 I agree this looks low-risk and valuable for debugging. Added to 1.14.0 blocker board. On 3/1/21, 10:06 AM, "Ernie Burghardt" wrote: I would like to include the change for GEODE-8919 to 1.14.0, it is a valuable and low risk change. Thanks, EB

[PROPOSAL] backport fix for GEODE-8919 to 1.14.0

I would like to include the change for GEODE-8919 to 1.14.0, it is a valuable and low risk change. Thanks, EB

Re: Cached regions are not synchronized after restore

The java client at least should automatically drop its cache when it loses and restores connectivity to all the servers. See https://geode.apache.org/docs/guide/12/developing/events/how_client_server_distribution_works.html#how_client_server_distribution_works__section_928BB60066414BEB9FAA7FB3120