Skip to content

Conversation

zuercher
Copy link
Member

@zuercher zuercher commented 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 #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: #4043

Signed-off-by: Stephan Zuercher stephan@turbinelabs.io

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>
…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>
@zuercher zuercher closed this Aug 6, 2018
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#4066. 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#4066

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>
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