envoyproxy / envoyproxy/envoy

move redis to TCP connection pool

Open
#3,818 6 comments 0 reactions 0 assignees View on GitHub
area/redis help wanted tech debt
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

Description

Tracking ticket for follow-on modifications related to the generic TCP connection pool, per discussion in #3747:

* [x] refactor HTTP1 connection pool to extend it
* [x] modify tcp_proxy to use connection pool vs. tcpConnForCluster
* [ ] modify redis_proxy to use connection pool

Other possible lines of inquiry:
* [ ] moving tcp_proxy drain manager into tcp conn pool (or perhaps cluster, per https://github.com/envoyproxy/envoy/pull/3938#discussion_r206261403)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.