[
https://issues.apache.org/jira/browse/ARTEMIS-4305?focusedWorklogId=931178&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-931178
]
ASF GitHub Bot logged work on ARTEMIS-4305:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/24 15:47
Start Date: 21/Aug/24 15:47
Worklog Time Spent: 10m
Work Description: iiliev2 commented on PR #4899:
URL:
https://github.com/apache/activemq-artemis/pull/4899#issuecomment-2302416406
I am not sure I understand why should `reconnect-attempts=0` be considered
better in our case.
All these are supposed to be valid configurations, right? In all cases we
are talking about a bug being fixed. We are perfeclty happy to use the current
configuration(prefer it infact, as it has been fairliy stable for some time,
apart for this one bug). Given that we've already spent so much resources on
fixing this bug, I do not see a reason to use another configuration which we
have to fix all over again.
Even if our current configuration is not the "best" one by some criteria,
why should this bug remain in the code?
Issue Time Tracking
-------------------
Worklog Id: (was: 931178)
Time Spent: 2.5h (was: 2h 20m)
> Zero persistence does not work in kubernetes
> --------------------------------------------
>
> Key: ARTEMIS-4305
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4305
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Ivan Iliev
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> In a cluster deployed in kubernetes, when a node is destroyed it terminates
> the process and shuts down the network before the process has a chance to
> close connections. Then a new node might be brought up, reusing the old
> node’s ip. If this happens before the connection ttl, from artemis’ point of
> view, it looks like as if the connection came back. Yet it is actually not
> the same, the peer has a new node id, etc. This messes things up with the
> cluster, the old message flow record is invalid.
> One way to fix it could be if the {{Ping}} messages which are typically used
> to detect dead connections could use some sort of connection id to match that
> the other side is really the one which it is supposed to be.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
