-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Issue 9195] Evict silos from cluster if they remain in the Joining or Created state for longer than MaxJoinAttemptTime #9201
Conversation
@dotnet-policy-service agree |
Currently looking at what tests I can modify to cover this or If I need to add a new one. |
ClusterHealthMonitorTests.cs may be a good fit. The test case there is large (too large), but adding a new test case or modifying the existing one is ok |
I added a test with |
I ended up refactoring the tests in Tests added:
Changes Related to the refactor:
private class ClusterHealthMonitorTestRig(
MembershipTableManager manager,
IClusterMembershipService membershipService,
IOptionsMonitor<ClusterMembershipOptions> optionsMonitor,
ClusterHealthMonitor.ITestAccessor testAccessor)
{
public readonly MembershipTableManager Manager = manager;
public readonly IClusterMembershipService MembershipService = membershipService;
public readonly IOptionsMonitor<ClusterMembershipOptions> OptionsMonitor = optionsMonitor;
public readonly ClusterHealthMonitor.ITestAccessor TestAccessor = testAccessor;
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that would help a lot when recovering a failed silo!
Fixes #9195
In this PR:
ClusterMembershipOptions.EvictWhenMaxJoinAttemptTimeExceeded
(default to true)MembershipTableSnapshot
for silos in a state ofCreated
orJoined
for longer thanClusterMembershipOptions.MaxJoinAttemptTime
Microsoft Reviewers: Open in CodeFlow