Open andreleblanc11 opened 5 months ago
This is weird... a delivery tag is associated with a message... it means there was a message 222 somewhere caught between the broker and the client, and the connection was torn down to get rid of it. So it indicates data loss of some sort.
Normally the point of recovering a connection is to recover such messages... so ... who remembered what? is the question... the client doesn't have any state, so where would it pull 222 from? very strange.
@andreleblanc11 do you remember what we did to recover from this?
I moved this comment about the PRECONDITION FAILED unknown delivery tag problem to https://github.com/MetPX/sarracenia/issues/953#issuecomment-2129676332
Encountered during auto-patching, when both brokers got rebooted on stage.
An instance, when trying to connect to the broker, may inadvertently get its AMQP connection restarted. The logs report back with an error message.