Re: HA failover: Nothing we try reduces client recovery below one minute

2024-02-23 Thread Marco Garavello
n > > > > > > > [image: rg] > <https://urldefense.com/v3/__https://www.redpointglobal.com/__;!!Ck4v2Rc!nzN3whXfPpxIweqDhJzenIYN05MWZUfHlopo7TBhpb6m8p-5EP7pvzzQD-SMZfQwgBJ_y4NGWq3NEStRIDMAEkW0wjT3tt3H50EbXg$> > > John Lilley > > Data Management Chief Architect

RE: HA failover: Nothing we try reduces client recovery below one minute

2024-02-21 Thread Vilius Šumskas
: users@activemq.apache.org Cc: Lino Pereira Subject: HA failover: Nothing we try reduces client recovery below one minute Greetings! We are having a devil of a time trying to reduce delay during a failover event. We’ve set our URL to (tcp://dm-activemq-live-svc:61616,tcp://dm-activemq-backup

Re: HA failover: Nothing we try reduces client recovery below one minute

2024-02-21 Thread Karl Weller
tcp_fin_timeout=10' >> /etc/sysctl.conf Hope this helps! From: John Lilley Sent: Wednesday, February 21, 2024 1:45 PM To: users@activemq.apache.org Cc: Lino Pereira Subject: HA failover: Nothing we try reduces client recovery below one mi

Re: HA failover: Nothing we try reduces client recovery below one minute

2024-02-21 Thread Justin Bertram
I would recommend a couple of things to narrow down the issue... First, have a script or something on the client gather thread dumps at regular intervals (e.g. every 5 seconds) starting right before you kill the pod and continuing until the client fails over and recovers. Second, turn on TRACE lo

HA failover: Nothing we try reduces client recovery below one minute

2024-02-21 Thread John Lilley
Greetings! We are having a devil of a time trying to reduce delay during a failover event. We’ve set our URL to (tcp://dm-activemq-live-svc:61616,tcp://dm-activemq-backup-svc:61617)?ha=true&reconnectAttempts=200&initialConnectAttempts=200&clientFailureCheckPeriod=1&connectionTTL=1&callTi