[ 
https://issues.apache.org/jira/browse/ARTEMIS-4305?focusedWorklogId=916557&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-916557
 ]

ASF GitHub Bot logged work on ARTEMIS-4305:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Apr/24 04:26
            Start Date: 26/Apr/24 04:26
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on PR #4899:
URL: 
https://github.com/apache/activemq-artemis/pull/4899#issuecomment-2078606956

   I think you could simplify this quite a bit. Here's what I suggest...
   
   - Don't modify any packet aside from `Ping` and only modify it with a new 
`byte[]`.
   - The broker should send its node ID in every `Ping`.
   - The first time the client receives a `Ping` it should save the node ID.
   - If a client ever receives a `Ping` that is different from the one it has 
saved then it should disconnect.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 916557)
    Time Spent: 20m  (was: 10m)

> 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: 20m
>  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)

Reply via email to