Revert "tcp_proxy: convert TCP proxy to use TCP connection pool (#3938)"#4043
Merged
mattklein123 merged 1 commit intomasterfrom Aug 3, 2018
Merged
Revert "tcp_proxy: convert TCP proxy to use TCP connection pool (#3938)"#4043mattklein123 merged 1 commit intomasterfrom
mattklein123 merged 1 commit intomasterfrom
Conversation
This reverts commit 028387a. Signed-off-by: Daniel Hochman <danielhochman@users.noreply.github.com>
mattklein123
approved these changes
Aug 3, 2018
Member
mattklein123
left a comment
mattklein123
left a comment
There was a problem hiding this comment.
Thanks for digging on this.
zuercher
added a commit
to turbinelabs/envoy
that referenced
this pull request
Aug 6, 2018
Converts TcpProxy::Filter and WebSocket::WsHandlerImpl to use Tcp::ConnectionPool to obtain connections. Much of the stats handling and connection timeouts are handled by the connection pool. Stats were manually verified by comparing stats produced by the tcp_proxy_integration_test with and without the connection pool change. This reapplies an earlier changed reverted due to envoyproxy#4043. That bug is fixed by performing the connection pools state management before forwarding callbacks. *Risk Level*: medium *Testing*: unit/integration testing *Docs Changes*: n/a *Release Notes*: n/a *Fixes*: envoyproxy#4043 Signed-off-by: Stephan Zuercher <stephan@turbinelabs.io>
zuercher
added a commit
to turbinelabs/envoy
that referenced
this pull request
Aug 6, 2018
…arding callbacks and tracking whether the connection has been invalidated or not (allowing the callback to use the connection to e.g., obtain a dispatcher). Signed-off-by: Stephan Zuercher <stephan@turbinelabs.io>
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
2 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.
Signed-off-by: Daniel Hochman danielhochman@users.noreply.github.com
This reverts commit 028387a, #3938.
After this PR was deployed to production, our instances would periodically experience a sharp and sustained uptick in CPU.
I removed traffic from one of the instances. It continued to consume 50% CPU. I took a perf capture to get the call stack which pointed me to this PR in the diff.
For fun I also generated a flame graph.