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

thrift proxy: move more of Router into RequestOwner #17376

Merged

Conversation

rgs1
Copy link
Member

@rgs1 rgs1 commented Jul 16, 2021

This is PR 2/4 towards implementing shadow requests for thrift.

This moves all the stats into the common RequestOwner interface so that
they can be reused. The next, similar sized, PR will decouple
UpstreamRequest from the Router so that it can be reused by the upcoming
ShadowRequest class.

The final PR should introduce the ShadowWriter and ShadowRequest classes
and make use of RequestOwner to tie them together.

Signed-off-by: Raul Gutierrez Segales [email protected]

This is PR 2/4 towards implementing shadow requests for thrift.

This moves all the stats into the common RequestOwner interface so that
they can be reused. The next, similar sized, PR will decouple
UpstreamRequest from the Router so that it can be reused by the upcoming
ShadowRequest class.

The final PR should introduce the ShadowWriter and ShadowRequest classes
and make use of RequestOwner to tie them together.

Signed-off-by: Raul Gutierrez Segales <[email protected]>
@rgs1 rgs1 requested a review from zuercher as a code owner July 16, 2021 00:17
Copy link
Member

@zuercher zuercher 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 zuercher merged commit 6acfb40 into envoyproxy:main Jul 19, 2021
leyao-daily pushed a commit to leyao-daily/envoy that referenced this pull request Sep 30, 2021
This is PR 2/4 towards implementing shadow requests for thrift.

This moves all the stats into the common RequestOwner interface so that
they can be reused. The next, similar sized, PR will decouple
UpstreamRequest from the Router so that it can be reused by the upcoming
ShadowRequest class.

The final PR should introduce the ShadowWriter and ShadowRequest classes
and make use of RequestOwner to tie them together.

Risk Level: low, refactor
Testing: existing tests pass
Docs Changes: n/a
Release Notes: n/a
Signed-off-by: Raul Gutierrez Segales <[email protected]>
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.

2 participants