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

Improved Client handling of failed RPCs #4106

Merged
merged 8 commits into from
Apr 5, 2018
Merged

Improved Client handling of failed RPCs #4106

merged 8 commits into from
Apr 5, 2018

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Apr 4, 2018

This PR improves the handling of failed RPCs by:

  1. Randomizing servers such that we don't repick the same server if they are
    being set from Consul.
  2. Trigger a retry when there is a sucessful RPC.

return true
} else if s == nil && o != nil || s != nil && o == nil {
return false
}
Copy link
Member

Choose a reason for hiding this comment

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

Can be shortened to if s == nil || o == nil { return s == o }

h/t to @chelseakomlo

equal := servers.Equal(m.servers)

// Randomize the incoming servers
servers.shuffle()
Copy link
Member

Choose a reason for hiding this comment

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

Do you still want to shuffle if they're equal?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah otherwise we will have deterministic ordering through Consul discovery.

dadgar added 4 commits April 5, 2018 10:58
Handle the ErrNoLeader case and apply slower retries. Also when we have
missed the heartbeat retry aggressively, backing off after we have
missed for more than 30 seconds.
@dadgar dadgar merged commit b2ae8b7 into master Apr 5, 2018
@dadgar dadgar deleted the b-servers branch April 5, 2018 20:48
@github-actions
Copy link

github-actions bot commented Mar 7, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 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