Skip to content
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

Clustering should be able to accurately handle passivation/handoff(rebalance) #190

Open
briansain opened this issue Mar 7, 2024 · 1 comment
Assignees

Comments

@briansain
Copy link
Contributor

Version Information
Version of Akkatecture?
Akkatecture.Cluster

Describe the bug
The framework does not handle passivation and handoff messages well. The default behaviour for Akka.Net is to send a PosionPill during passivation/handoff (rebalance). Since there are layers to the aggregates/entities, the shard actor doesn't get notification of complete passivation/handoff which leads to an instable state.

Expected behavior
If a shard wants to passivate an idle entity or rebalance a shard, then the shard to be aware of when the process is completed on that aggregate(s).

Actual behavior
Aggregates are passivating, but the stashed state of the entity within the actor shard remains in the passivating state.

Environment
Docker

@briansain briansain self-assigned this Mar 7, 2024
@malclear
Copy link
Contributor

I'll look at this this coming week, Brian. If you'd like to and have time to talk about it, reach out through Discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants