router: fix data race and refactor - #6673
Closed
MakostaDev wants to merge 1 commit into
Closed
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Member
|
我重写一份吧 #6678 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This currently could trigger a data race between gRPC API calls and
pickRouteInternal(), as well as in several balancer functions that look up a balancer by tag.ReloadRules()also had an issue: if it failed partway through, rules and balancers that had already been written stayed in place. I changed it to validate and build the new rules/balancers first, and only swap them in afterward. So on error, the router is left in its original, unchanged state.A few other functions were also cleaned up for a simpler implementation