You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Dapr recovers from an unhealthy state, it shouldn't run into a fatal error while trying to unlock an unlocked mutex.
Actual Behavior
We have different services that run into that behaviour from time to time. The dapr container enters an unhealthy state (for unknown reason) and after it enters the healthy state again, it runs into an fatal error: sync: unlock of unlocked mutex. I have attached the log.
In what area(s)?
What version of Dapr?
Expected Behavior
When Dapr recovers from an unhealthy state, it shouldn't run into a fatal error while trying to unlock an unlocked mutex.
Actual Behavior
We have different services that run into that behaviour from time to time. The dapr container enters an unhealthy state (for unknown reason) and after it enters the healthy state again, it runs into an fatal error: sync: unlock of unlocked mutex. I have attached the log.
slotbooking-service-868d448f46-6kj59.log
The good part is, that the container successfully recovers from it.
Steps to Reproduce the Problem
Release Note
The text was updated successfully, but these errors were encountered: