Skip to content

Conversation

@botengyao
Copy link
Member

@botengyao botengyao commented May 30, 2025

Added a load shed point when trying to create new connection in the connection pool.

Commit Message:
Additional Description:
Risk Level: low
Testing:
Docs Changes:
Release Notes:

Signed-off-by: Boteng Yao <boteng@google.com>
@repokitteh-read-only
Copy link

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #39685 was opened by botengyao.

see: more, trace.

botengyao added 2 commits May 30, 2025 17:57
…d_shed_point

Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
@botengyao botengyao changed the title conn pool load shed: added a new lsp to connection pool when creating new connections to upstream conn pool: added a new load shed when creating new connections to upstream May 30, 2025
botengyao added 11 commits June 2, 2025 20:15
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
Signed-off-by: Boteng Yao <boteng@google.com>
@botengyao botengyao marked this pull request as ready for review June 5, 2025 20:35
@botengyao botengyao requested a review from yanavlasov June 5, 2025 20:35
@botengyao
Copy link
Member Author

/assign @yanavlasov

Copy link
Contributor

@yanavlasov yanavlasov left a comment

Choose a reason for hiding this comment

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

/wait-any

return nullptr;
} else if (result == ConnectionResult::LoadShed) {
pending->cancel(Envoy::ConnectionPool::CancelPolicy::CloseExcess);
onPoolFailure(nullptr, absl::string_view(), ConnectionPool::PoolFailureReason::Overflow,
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to create a new failure reason so we can distinguish load shed from just pool limits overflow?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, I think that totally makes sense, and I tend to add an OverloadManager, but I realized that it will change a lot of other places that is associated with the enum, would you be okay to add a TODO that I will change it latter?

Signed-off-by: yanavlasov <yavlasov@google.com>
@yanavlasov yanavlasov enabled auto-merge (squash) June 10, 2025 18:03
@yanavlasov yanavlasov merged commit a13e249 into envoyproxy:main Jun 10, 2025
24 checks passed
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