Skip to content

Conversation

@fishy
Copy link
Contributor

@fishy fishy commented Feb 2, 2022

This seems to be triggered by envoy closing the connections differently
from thrift servers.

@fishy fishy requested a review from a team as a code owner February 2, 2022 20:18
@fishy fishy requested review from konradreiche and kylelemons and removed request for a team February 2, 2022 20:18
@fishy
Copy link
Contributor Author

fishy commented Feb 2, 2022

Alternatively we can also do it here, @kylelemons & @konradreiche do you have a strong preference either way?

@fishy
Copy link
Contributor Author

fishy commented Feb 2, 2022

💇 moved the fix to clientpool so it's more foolproof (for example, in the future we no longer wrap clients with ttlClient).

@fishy fishy changed the title Fix connect leak from thriftbp.ttlClient Fix connect leak from clientpool Feb 2, 2022
@fishy
Copy link
Contributor Author

fishy commented Feb 3, 2022

💇 added the fix to another place, which is the actual one triggered by envoy.

It's also fixed upstream in thrift and will be part of thrift 0.16.0,
but the double fix is harmless and will help us when it's used on older
thrift versions.
@fishy fishy merged commit b1ba649 into reddit:master Feb 4, 2022
@fishy fishy deleted the fix-connect-leak branch February 4, 2022 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants