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

Slow start Configuration Not Working as Expected #37197

Open
ashishyadav-meesho opened this issue Nov 18, 2024 · 1 comment
Open

Slow start Configuration Not Working as Expected #37197

ashishyadav-meesho opened this issue Nov 18, 2024 · 1 comment
Labels

Comments

@ashishyadav-meesho
Copy link

Title: Slow start Configuration Not Working as Expected

Description:
Issue: We have configured slow start for some of our services but have observed two different behaviors across pods. While some pods are honoring the slow start as expected, others are taking significantly longer to ramp up to full capacity. It would be greatly appreciated if you could help identify whether this is due to a configuration issue or a potential issue with Envoy.

Repro steps:
Setup contour envoy as a deployment running three instances of contour and envoy as proxy, We are running contour version: 1.27.2 and envoy image is: docker.io/bitnami/envoy:1.27.2-debian-11-r1

Slow Start configuration:
image

Request Metrics:
Screenshot 2024-11-18 at 2 04 22 PM

382668784-68663c67-2da4-433a-bfa7-05241ea24d3f
@ashishyadav-meesho ashishyadav-meesho added bug triage Issue requires triage labels Nov 18, 2024
@nezdolik
Copy link
Member

nezdolik commented Nov 18, 2024

@ashishyadav-meesho I will need more information to be able to debug:

  1. please attach Envoy (not contour) config, you could get it from http://{$ENVOY_POD_IP}:{$ADMIN_PORT}/config_dump
  2. output from clusters endpoint (that concerns this specific cluster), you could get it from http://{$ENVOY_POD_IP}:{$ADMIN_PORT}/clusters
  3. was there any change of pod health status during the time when you experienced issue with slow start?

@soulxu soulxu removed the triage Issue requires triage label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants