Client connection closed after crc validation error #8972
Replies: 3 comments 3 replies
-
CRC checks are performed only in one place and they can indicate genuine on disk file corruption. RabbitMQ cannot avoid There was an incorrectly performed check in Ra that affected quorum queues on Erlang 26. It was addressed a few months ago. I do not remember seeing this in the context of streams that use a different library, Osiris. Can you share the segment files of the stream in question? There is no other way for us to perform root cause analysis. |
Beta Was this translation helpful? Give feedback.
-
@michaelklishin I couldn't find stream file with the exact chunk id but this one had a closest modification date |
Beta Was this translation helpful? Give feedback.
-
I noticed this PR by @kjnilsson rabbitmq/osiris#137 that may be related to this issue. It got included in osiris v1.6.4 which made it to rabbitmq 3.12.5. I'll post an update after some testing. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Version 3.12.2
erlang 25.0.4
os ubuntu 20.04
Occasionally an application using https://github.com/rabbitmq/rabbitmq-dotnet-client subscribing to a stream on a 3 node cluster via AMQP 0.9.1 subscription will get a channel close
A server log indicates an erlang process crash with
crc validation failure at chunk id...
and supervisor terminating the child due to max restart intensity.The cluster is sufficiently provisioned and in the moment of crash was running without other problems.
Possibly related to https://groups.google.com/g/rabbitmq-users/c/29yEH-2F3hc/m/BQtGQstqCAAJ
Reproduction steps
No idea. It happens from time to time. The client restarts and reconnects with no persisting problem
Expected behavior
No crash
Additional context
server log:
rabbitmq-server-8972-server-log.txt
Beta Was this translation helpful? Give feedback.
All reactions