Hey there Geode-Devs,
It has come to my attention that there have been a few commits that have
creeped into the `develop` branch that don’t follow a standard that we have set.
I would like to make every committer and contributor aware of the following
code of conduct we have all agreed to:
htt
Thanks Juan!
I will check it.
Alberto
From: Ju@N
Sent: Thursday, July 2, 2020 7:46 PM
To: dev@geode.apache.org
Subject: Re: Question about gateway sender stopped and memory consumption
I recall some discussion about this in the past, there even was an "RFC"
tha
Thanks for your answer, Kirk.
If we persist the unsent events in a persistent region then the memory consumed
would not be as high but still it would not solve our problem with long lasting
split brain as the persistent region would take some memory too to store those
events even if they were o
I recall some discussion about this in the past, there even was an "RFC"
that never got implemented:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=80452478.
Best regards.
On Thu, 2 Jul 2020 at 18:41, Kirk Lund wrote:
> I would have expected unsent events to be stored in a queu
I would have expected unsent events to be stored in a queue that is backed
by a persistent region or something on disk. If that's not currently true,
then it seems like a good direction might be to make tmpDroppedEvents use a
durable queue of some sort that overflows to disk.
On Thu, Jul 2, 2020
Hi,
We have observed that when a gateway sender is stopped in a site, all the
events received while it is stopped are stored in the
'AbstractGatewaySender.tmpDroppedEvents' queue of the primary sender. The
elements of this queue are not removed from this queue until the sender is
started back
Hi community,
For some of our coordination efforts, like release status updates,
coordination of flaky tests or collective debugging of some issues a more
synchronous medium might be useful. We've had an Apache Geode Slack channel
for a long time, but never used it much. I wonder if it would be wo
