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

Akka.Cluster.Tools: ClusterSingleton should factor in AppVersion when choosing next likely home for messages during deployments #6035

Closed
Aaronontheweb opened this issue Jul 8, 2022 · 0 comments · Fixed by #6065

Comments

@Aaronontheweb
Copy link
Member

Is your feature request related to a problem? Please describe.

Akka.Cluster.Sharding does this currently - shards are homed onto nodes with the highest AppVersion when a deployment is detected inside the cluster. This helps us guarantee that we aren't allocating shards, again, on locations that are going to be removed later during a deployment.

We do not do this for Akka.Cluster singletons, which have the same issue as sharded entity actors: they prefer to be moved only once if possible.

Describe the solution you'd like

Consider AppVersion in the re-homing calculation for cluster singletons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant