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

The backend service warm-up using Ingress Gateway is not meeting expectations #48816

Closed
2 tasks done
xlq20080808 opened this issue Jan 16, 2024 · 2 comments
Closed
2 tasks done
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@xlq20080808
Copy link

xlq20080808 commented Jan 16, 2024

Is this the right place to submit this?

  • This is not a security vulnerability or a crashing bug
  • This is not a question about how to use Istio

Bug Description

I have a backend service that utilizes IngressGateway with warmup configured. The warmup window is set to 30 seconds, and locality load balancing is disabled. However, there seems to be an issue where the traffic warmup time for a pod is significantly greater than the configured 30 seconds.
image
The configuration for the VirtualService is as follows

trafficPolicy:
    loadBalancer:
      localityLbSetting:
        enabled: false
      warmupDurationSecs: 30s

Version

istio control plane version: 1.16.5
istio data plane version: 1.16.5

Additional Information

No response

@howardjohn
Copy link
Member

Istio 1.16 is EOL. Please upgrade and see if the issue persists

@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Apr 16, 2024
@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2024-01-16. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

3 participants