Hi again,
Status update: the simplification of the maps suggested by Jacob made useless
the new proposed class containing the ServerLocation and the member id. With
this refactoring, replication is working in the scenario we have been
discussing in this conversation. Thats great, and I think th
My initial guess without looking is that the client pool is sending a ping to
each ServerLocation on only one of the available Connections. This logic should
be changed to send to each unique member, since ServerLocation is not unique
anymore.
-Jake
> On Jan 27, 2020, at 8:55 AM, Alberto Bust
Hi Mario,
That bug number is from an old version of GemFire before it was open
sourced as geode.
Looking at some of the old bug info, it looks like the bug had to do with
the fact that calling stop on the region was causing there to be unexpected
RegionDestroyedException's to be thrown when the q
Some additional info/context from the PR that is blocked by this issue:
Although we have GFSH stop, it can still be used on an individual node. We
just publish a caution, but it looks like we still allowed it due to having
some users using it:
CAUTION: Use caution with the stop gateway-sender co
