on in geode-native
Thanks,
Mario.
From: Mike Martell
Sent: Thursday, March 4, 2021 10:00 PM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Here's the doc I was referring (the one Dan mentioned) to:
https://geode.apach
for keys in which the client has registered interest.
geode.apache.org
From: Mike Martell
Sent: Thursday, March 4, 2021 9:31 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Actually, I believe that is correct. I.e., clients
e would be no
need to invalidate that data even if the cluster had to be restored.
From: Mario Salazar de Torres
Sent: Thursday, March 4, 2021 9:19 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Hi Mike,
Thanks for lo
___
De: Mike Martell
Enviado: Thursday, March 4, 2021 6:13:19 PM
Para: dev@geode.apache.org
Asunto: Re: Cached regions are not synchronized after restore
It seems like this is a NC bug. I'll write a test for your scenario, but it
seems like the NC is not dropping its local cache (i.e., c
which is implied by a
restore operation. I'll report back on my findings.
Mike
From: Mario Salazar de Torres
Sent: Thursday, March 4, 2021 1:34 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Hi,
Well, thing i
_
From: Mario Salazar de Torres
Sent: Thursday, March 4, 2021 10:34 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Hi,
Well, thing is Mike you raised an interesting topic here, because I wasn't
seeing the behavior of GF_CACHE_CONCURRENT_MODIFIC
the same time. But in this case, they are
received at two distant points in time (before the restart and after the
restart).
Why is this happening? As you can see both versions have the same
"entry_version" (1), so in this case for both Java and native clients what
determines w
much nicer!
Thanks,
Mike.
From: Mario Salazar de Torres
Sent: Monday, March 1, 2021 6:38 PM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
Hi everyone,
After replicating the test with both clients being the Java implementation, I
could ve
s.html#how_client_server_distribution_works__section_928BB60066414BEB9FAA7FB3120334A3
-Dan
From: Jacob Barrett
Sent: Friday, February 26, 2021 9:29 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
For clarification, does the a Java client show the same behavior in missi
#how_client_server_distribution_works__section_928BB60066414BEB9FAA7FB3120334A3
-Dan
From: Jacob Barrett
Sent: Friday, February 26, 2021 9:29 AM
To: dev@geode.apache.org
Subject: Re: Cached regions are not synchronized after restore
For clarification, does the a Java client show the same behavior in missing the
events after restore
For clarification, does the a Java client show the same behavior in missing the
events after restore or is this something you are saying is unique to the
native clients?
> On Feb 26, 2021, at 4:48 AM, Mario Salazar de Torres
> wrote:
>
> Hi,
> These months I have been tackling a series of iss
11 matches
Mail list logo
