-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Router crash on sys_mutex_unlock #1134
Comments
This appears to be a race involving the Q2 unblock handler. What I believe is happening is that the upstream (ingress) TCP connection is being force-closed while in Q2 blocked state. That TCP connection is freed, but the downstream connection (AMQP inter-router) has just drained the ingress message buffers to relieve the Q2 block. This causes the downstream connection to invoke the Q2 unblock handler registered with the message by the upstream TCP connection. Since that connection has just been freed the handler faults when it attempts to manipulate the upstream TCP connection. Here is a traceback of the crash:
|
In our Longevity machine, we have a iperf test running for the last 4 days, and we got 11 router restarts
The test runs in 3 namespaces (public1, public2, private1), created in a single CRC cluster.
Each namespace has an iperf server exposed, but the client runs in the private1 NS.
We send requests for all the 3 services, forever, using this commands :
These are the images we are using in this test :
The text was updated successfully, but these errors were encountered: