+1
From: Alexander Murmann
Sent: Thursday, July 29, 2021 11:00 AM
To: geode
Subject: August Community Meeting
Hi Geode community,
Next week's August 4th is the first Wednesday in August. Usually that would be
the day that we have our community meeting. Many of
I reproduced your issue with your scripts.
They do:
create gateway-receiver
create disk-store
create gateway-sender
create region
With that order, I see the hang you mentioned. I'm not 100% sure why that is
happening but you can prevent it by reordering these elements.
As Anil said, you
Alberto,
I'd have to see thread dumps on all the members on the site that has the stuck
thread, but that sounds like you're hitting the limitation with conserve
sockets and WAN. Are any of the stuck threads shared P2P message readers? If
so, that is almost definitely a distributed deadlock.
Alberto,
There are a lot of applications that use this property, so I wouldn't expect it
to be removed.
Here is some additional detail regarding this property:
The default behavior is if a sender in one site can connect successfully to a
receiver in another and send batches to it, the acks
great find. Will there be dedicated channel for communication
from the node where conserve-socket is set to false to the remote nodes.
-Anil.
On 12/2/20, 3:14 PM, "Barrett Oglesby" wrote:
I ran a bunch of tests using the long-running-test code where the
servers had a mix
I ran a bunch of tests using the long-running-test code where the servers had a
mix of conserve-sockets settings, and they all worked ok.
One set of tests had 6 servers - 3 with conserve-sockets=false and 3 with
conserve-sockets=true.
Another set of tests had 4 servers - 3 with
+1
From: Xiaojian Zhou
Sent: Tuesday, September 29, 2020 3:09 PM
To: dev@geode.apache.org
Subject: [PROPOSAL] Backport GEODE-6008 to support 1.12
Hi,
GEODE-6008 changed “java.lang.IllegalStateException: NioSslEngine has been
closed” to IOException, which
Steve,
Here are some ways to access these statistics using JMX.
To access JVM metrics for a member including heap usage using JMX, invoke the
MemberMXBean showJVMMetrics operation.
These values are gotten from ManagementFactory.getMemoryMXBean(),
ManagementFactory.getThreadMXBean() and
I think you've found a bug in this scenario. The
ParallelGatewaySenderQueue.addShadowPartitionedRegionForUserPR method currently
compares the data policy of the input region's leader region with the sender's
persistence policy. It assumes the input region and the leader region have the
same
