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

Rewrite linkerd-tcp #63

Merged
merged 4 commits into from
Jun 13, 2017
Merged

Rewrite linkerd-tcp #63

merged 4 commits into from
Jun 13, 2017

Conversation

olix0r
Copy link
Member

@olix0r olix0r commented Jun 10, 2017

linkerd-tcp 0.1.0 constitues a major rewrite.

Previously, linkerd-tcp did not properly utilize tokio's task model, which lead
to a number of performance and correctness problems. Furthermore, linkerd-tcp's
configuration interface was substantially different from linkerd's, which
caused some confusion.

Now, linkerd-tcp has been redesigned:

  • to better-leverage tokio's reactor;
  • to support connection and stream timeouts;
  • to provide much richer metrics insight;
  • to be structured like a linkerd-style router;
  • general correctness improvements.

Fixes #26 #40 #49 #50
Depends on linkerd/tacho#20

linkerd-tcp 0.1.0 constitues a major rewrite.

Previously, linkerd-tcp did not properly utilize tokio's task model, which lead
to a number of performance and correctness problems. Furthermore, linkerd-tcp's
configuration interface was substantially different from linkerd's, which
caused some confusion.

Now, linkerd-tcp has been redesigned:
- to better-leverage tokio's reactor;
- to support connection and stream timeouts;
- to provide much richer metrics insight;
- to be structured like a linkerd-style router;
- general correctness improvements.

Fixes #26 #40 #49 #50
Depends on linkerd/tacho#20
enable per-client max_waiters and min_connections settings

- Don't do connection backoffs. They weren't thought out well.
- Don't use consecutive failures to assess load.
- Add fail fast.
- Remove balancer::Updater, because the dispatcher task needs to be notified on resolutions.
- Make Ctx RAII again

don't do overcomplicated probabalistic p2c. just simple lowest-score-wins

handle failures properly when updating from service discovery
@olix0r olix0r merged commit 323c9f8 into master Jun 13, 2017
@olix0r olix0r deleted the ver/0.1.0 branch June 13, 2017 20:34
@olix0r olix0r removed the reviewable label Jun 13, 2017
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.

1 participant