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

kv: Set default SendNextTimeout to a reasonable value #6728

Merged
merged 1 commit into from
May 16, 2016

Conversation

bdarnell
Copy link
Contributor

@bdarnell bdarnell commented May 16, 2016

Reverts #2973, which was a workaround for issues that have been more
cleanly resolved in #6688.


This change is Reviewable

@tamird
Copy link
Contributor

tamird commented May 16, 2016

science dog says LGTM

@tbg
Copy link
Member

tbg commented May 16, 2016

LGTM

@tbg
Copy link
Member

tbg commented May 16, 2016

Still wonder about that value - does that make sense/should there be a TODO about optimizing it?

Reverts cockroachdb#2973, which was a workaround for issues that have been more
cleanly resolved in cockroachdb#6688.
@bdarnell
Copy link
Contributor Author

500ms seems high to me, but that's where it was before. Added a TODO and a comment on #6719.

@bdarnell bdarnell merged commit fe7b2b6 into cockroachdb:master May 16, 2016
@bdarnell bdarnell deleted the retry-timeouts branch May 16, 2016 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants