Skip to content

tcp/conn_pool: improve interface for callers#3903

Merged
zuercher merged 3 commits intoenvoyproxy:masterfrom
turbinelabs:stephan/prep-tcp-conn-pool-for-tcp-proxy
Jul 23, 2018
Merged

tcp/conn_pool: improve interface for callers#3903
zuercher merged 3 commits intoenvoyproxy:masterfrom
turbinelabs:stephan/prep-tcp-conn-pool-for-tcp-proxy

Conversation

@zuercher
Copy link
Member

Provides additional pool failure reasons to allow Tcp::ConnectionPool
callers to distinguish between time outs and connection failures.
Passes through connection and buffer watermark events.

A subsequent PR will switch the TCP proxy to use the TCP connection
pool (and makes use of these features). Relates to #3818.

Risk Level: low
Testing: unit tests
Docs Changes: n/a
Release Notes: n/a

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

Provides additional pool failure reasons to allow Tcp::ConnectionPool
callers to distinguish between time outs and connection failures.
Passes through connection and buffer watermark events.

A subsequent PR will switch the TCP proxy to use the TCP connection
pool (and makes use of these features). Relates to envoyproxy#3818.

*Risk Level*: low
*Testing*: unit tests
*Docs Changes*: n/a
*Release Notes*: n/a

Signed-off-by: Stephan Zuercher <stephan@turbinelabs.io>
ggreenway
ggreenway previously approved these changes Jul 23, 2018
Copy link
Member

@ggreenway ggreenway left a comment

Choose a reason for hiding this comment

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

LGTM

@zuercher
Copy link
Member Author

@mattklein123 or @alyssawilk do you want to have a look?

Copy link
Contributor

@alyssawilk alyssawilk left a comment

Choose a reason for hiding this comment

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

Looks good to me - only one nit on my end.

ConnectionFailure
// A local connection failure took place and the connection could not be bound.
LocalConnectionFailure,
// A remote connection failure took place and the connection could not be bound.
Copy link
Contributor

Choose a reason for hiding this comment

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

when we say bound here, we mean bound to an Envoy client connection rather than a literal bind() call right?

If so could we rephrase to make that more clear?

Copy link
Member Author

Choose a reason for hiding this comment

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

Will do

@mattklein123
Copy link
Member

LGTM from quick skim. Happy to defer to @ggreenway and @alyssawilk. Excited to see all this code converge.

zuercher added 2 commits July 23, 2018 12:44
Signed-off-by: Stephan Zuercher <stephan@turbinelabs.io>
…e reasons

Signed-off-by: Stephan Zuercher <stephan@turbinelabs.io>
@zuercher zuercher merged commit 7c11e92 into envoyproxy:master Jul 23, 2018
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.

4 participants