You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2021/12/15 13:59:00 UTC
[jira] [Closed] (ARTEMIS-3496) Replica connection to its live should fail fast
[ https://issues.apache.org/jira/browse/ARTEMIS-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic closed ARTEMIS-3496.
------------------------------------
> Replica connection to its live should fail fast
> -----------------------------------------------
>
> Key: ARTEMIS-3496
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3496
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.20.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Both SharedNothingBackupActivation and ReplicationBackupActivation set session factory's cluster control reconnect attempts to 1, but the comment on the code for the former says:
> {code:java}
> //we should only try once, if its not there we should move on.
> {code}
> That doesn't look right, indeed, in case of failed cluster connection due to TTL, the additional attempt to reconnect slow down the whole failover process.
> As per the comment, to try connect just once, reconnect attempts should be set to 0.
> The weird thing is that the same session factory is created (along with the initial connection) with reconnectAttempts == 0 by ClusterController::connectToNodeInReplicatedCluster, before authorizing and starting the initial sync.
> Need an investigation to find out why it seems to be set to 1 from the original correct value.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)