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

Improve usability of custom grain placement configuration #4102

Merged
merged 1 commit into from
Mar 6, 2018

Conversation

ReubenBond
Copy link
Member

Fixes #4098

@ReubenBond ReubenBond added this to the 2.0.0 milestone Mar 1, 2018
@ReubenBond ReubenBond requested a review from jason-bragg March 1, 2018 01:40
@ReubenBond
Copy link
Member Author

@dotnet-bot test functional

@@ -3,7 +3,7 @@
namespace Orleans.Runtime
{
[Serializable]
internal class ActivationCountBasedPlacement : PlacementStrategy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason for making all these built-in strategies public? Seems like it's not something that application code will need to reference.

@sergeybykov
Copy link
Contributor

To expand on my comment. These are built-in placement policies, and I think it's a bad idea to let application code override their behavior because, for example, it would be very difficult to figure out in the logs why a well known placement strategy causes very different placement decisions. It is better to be explicit and introduce new strategies for new placement directors, so that there is no confusion. Hence, I think the built-in strategies should stay immutable.

@ReubenBond ReubenBond force-pushed the fix-placement-registration branch from 6d2b4a4 to f2d3bbe Compare March 6, 2018 03:34
@ReubenBond
Copy link
Member Author

All fixed :)

@sergeybykov sergeybykov merged commit b556bf3 into dotnet:master Mar 6, 2018
@ReubenBond ReubenBond deleted the fix-placement-registration branch March 6, 2018 04:56
@github-actions github-actions bot locked and limited conversation to collaborators Dec 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants