-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Exceeding max-concurrent-recoveries triggers circuit breaker #6106
Labels
Milestone
Comments
Looks like @ismaelhamed has a fix for this targeting the v1.5 branch - we'll see if we can also backport that to a future v1.4 release as well. Going to review Ismael's work along with @Arkatufus right now. |
@ismaelhamed @Aaronontheweb I was able to retrieve some errors today which include a more detailed stack trace. I'm posting it here, in case it helps identifying if it's actually related to #6109
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version Information
Version of Akka.NET? 1.4.40
Which Akka.NET Modules? Akka.Cluster.Sharding 1.4.40, Akka.Persistence.SqlServer 1.4.35
Describe the bug
In certain situations, exceedeing temporarily the max-concurrenct-recoveries parameter triggers a circuit breaker that prevents Akka Persistence to persist any further events for the duration of the circuit breaker.
See sequence of logged events here:
I have been unable to reproduce reliably this problem, as it seems to happen fairly randomly on our production instance (a few times per day).
Setting locally a max-concurrenct-recoveries equal to 1 and force recover of multiple actor at once does not seem to create the issue, so it must be triggered by a combination of factors.
We can't find the root of the error that triggers the circuit breaker. There is no information in the logged OpenCircuitException, and that's the only error that appears in the log (hundreds of times for the duration of the open circuit breaker).
To Reproduce
I don't have reliable steps to trigger the problem.
I would appreciate hints on what I could try to understand better the underlying problem and come up with a strategy to reproduce reliably. It may be possible that this is entirely caused by some bad programming on my side, but I'm a bit lost in what to look for.
Environment
Windows on .NET 6
The text was updated successfully, but these errors were encountered: