ems that this closing inactive connection is done by Kubernetes as we
> run Geode on it.
>
> BR,
> Mario
>
>
> Šalje: Barry Oglesby
> Poslano: 22. studenog 2019. 22:35
> Prima: Mario Kevo
> Kopija: dev@geode.apache.org
> Predmet: Re
a: dev@geode.apache.org
Predmet: Re: Odg: Restart gateway-receiver
> If we don't send any event, the connection will be closed after some time as
> connection is inactive.
Are you seeing this behavior? I don't think this is true by default.
AbstractRemoteGatewaySender.initProxy sets these fie
ion if there is a some problem with network or
> it is just closed due to inactivity?
> Can we monitor the replication on some other way than looking
> "isConnected" state on JMX?
>
> BR,
> Mario
> ------
> *Šalje:* Barry Oglesby
> *Pos
ache.org
Predmet: Re: Restart gateway-receiver
Mario,
Thats the current behavior. When the sender is initially started, it
attempts to connect to the receiver. If it does not connect, it won't retry
until there is a batch of events to send. Look for callers of
GatewaySenderEventRemoteDispatch
After creating gateways senders and receivers between two geode clusters
> replications is established. After restart gateway receiver, sender will
> not connect to it until we send some entry from sender to receiver.
> Is this a normal behavior or a bug?
> Should geode have some mechanism
Hi geode dev,
After creating gateways senders and receivers between two geode clusters
replications is established. After restart gateway receiver, sender will not
connect to it until we send some entry from sender to receiver.
Is this a normal behavior or a bug?
Should geode have some
