[
https://issues.apache.org/jira/browse/ARTEMIS-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated ARTEMIS-3496:
-------------------------------------
Description:
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 with
reconnectAttempts == 0 (and a connection is established too) on with
ClusterController::connectToNodeInReplicatedCluster.
Need an investigation to find out why it seems to be set to 1 from the original
correct value.
was:
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 with
reconnectAttempts == 0. Need an investigation to find out why it seems to be
set to 1 from the original correct value.
> 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
>
> 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 with
> reconnectAttempts == 0 (and a connection is established too) on with
> ClusterController::connectToNodeInReplicatedCluster.
> 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.3.4#803005)
