[
https://issues.apache.org/jira/browse/ARTEMIS-4305?focusedWorklogId=931586&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-931586
]
ASF GitHub Bot logged work on ARTEMIS-4305:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Aug/24 21:33
Start Date: 23/Aug/24 21:33
Worklog Time Spent: 10m
Work Description: jbertram closed pull request #4899: ARTEMIS-4305 Zero
persistence does not work in kubernetes
URL: https://github.com/apache/activemq-artemis/pull/4899
Issue Time Tracking
-------------------
Worklog Id: (was: 931586)
Time Spent: 3h (was: 2h 50m)
> 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: 3h
> 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
