Skip to content

Update Cluster AutoDiscovery after failover#1684

Merged
NickCraver merged 2 commits intoStackExchange:mainfrom
laurauzcategui:laurau/address_update_node_relations_onfailover
Jun 15, 2021
Merged

Update Cluster AutoDiscovery after failover#1684
NickCraver merged 2 commits intoStackExchange:mainfrom
laurauzcategui:laurau/address_update_node_relations_onfailover

Conversation

@laurauzcategui
Copy link
Contributor

The following commits address: #1659

Where basically after manual failover the replicas endpoint list is
not refreshed.

ServerSelectionStrategy.cs

Updated:

  • SetClusterConfiguration to call new method UpdateNodeRelations with
    the configuration
    Added:
  • UpdateNodeRelations to have the same update logic that it was
    before in SetClusterConfiguration so it could be used in
    ConnectionMultiplexer

ConnectionMultiplexer.cs
Updated:

  • GetEndpointsFromClusterNodes, to call UpdateNodeRelations and
    refresh the configuration before returning the endpoints list

laurauzcategui and others added 2 commits February 10, 2021 17:43
  The following commits address: StackExchange#1659

  Where basically after manual failover the replicas endpoint list is
not refreshed.

  ServerSelectionStrategy.cs

  Updated:
   - SetClusterConfiguration to call new method UpdateNodeRelations with
the configuration
  Added:
   - UpdateNodeRelations to have the same update logic that it was
before in SetClusterConfiguration so it could be used in
ConnectionMultiplexer

   ConnectionMultiplexer.cs
   Updated:
   - GetEndpointsFromClusterNodes, to call UpdateNodeRelations and
refresh the configuration before returning the endpoints list
Copy link
Collaborator

@NickCraver NickCraver left a comment

Choose a reason for hiding this comment

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

Verified the symptoms locally and explains one test condition - pulling in!

Thank you!!

@NickCraver
Copy link
Collaborator

@TimLovellSmith @philon-msft can disregard here, we're good to go on next release, was able to (accidentally) cause the case this is resolving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants