[
https://issues.apache.org/jira/browse/ARTEMIS-3496?focusedWorklogId=663433&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-663433
]
ASF GitHub Bot logged work on ARTEMIS-3496:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Oct/21 10:25
Start Date: 11/Oct/21 10:25
Worklog Time Spent: 10m
Work Description: gemmellr commented on pull request #3771:
URL: https://github.com/apache/activemq-artemis/pull/3771#issuecomment-939896655
Main comment, without looking at the code, the tests all hung and caused the
GHA job to time out after 6 hours.
The tests should have an appropriate timeout to stop any one test taking an
excessive amount of time before failing (also makes clear which one goes bang
when they do, aiding following analysis of what happened).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 663433)
Time Spent: 1h 50m (was: 1h 40m)
> 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
> Time Spent: 1h 50m
> 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.3.4#803005)
