-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Daprd deleting actors unexpectedly #7734
Comments
2 things:
|
@grizzlybearg The reason we have to have a |
In what area(s)?
What version of Dapr?
Expected Behavior
My app uses the actor component. The actor in our code has a timer that is triggered at regular intervals. My expectation is that the timer is expected to be triggered without the daprd deleting the actors.
I also expect the daprd container to be able to conduct a healthz check on the actor without failure.
Actual Behavior
The daprd logs show the following log:
This message tends to happen during the creation of the actor for the first time or when a timer callback is invoked. Immediately after this log message appears, all actors are deleted (deactivated). When having thousands of actors, recovery of these actors is compute intensive given that there's a lot of data associated with each actor. Therefore, it would be ideal if we stopped the random deactivation of actors. I have been unable to deactivate the actor
healthz
check.I've confirmed that our internal code works without any issues (even without dapr (single processs runtime)), therefore, that is not a reason for the daprd runtime to delete actors.
Notes:
I do know that dapr creates the healthz endpoint for the actor component automatically:
I've confirmed that the healthz url is working
Steps to Reproduce the Problem
Our internal code isn't public but I can share the docker compose file that we are using for dev to CICD
Our internal code is inspired by the dapr example found at: https://github.com/dapr/python-sdk/tree/release-1.0/examples/demo_actor
The text was updated successfully, but these errors were encountered: