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

cluster-autoscaler fails to backoff when max-node-provision-time is 5 minutes leaving orphaned EC2 instance requiring manual termination #6810

Open
charlesritchea opened this issue May 9, 2024 · 3 comments
Labels
area/cluster-autoscaler kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@charlesritchea
Copy link

charlesritchea commented May 9, 2024

Which component are you using?:
cluster-autoscaler

What version of the component are you using?:
1.28.4

Component version:

What k8s version are you using (kubectl version)?:
1.28

What environment is this in?:

AWS EKS

What did you expect to happen?:

g4dn-2xlarge ASG timed out after max-node-provision-time of 5 minutes during scale up
I'd expect the EC2 instance that was scaled up to eventually be marked as unhealthy, then eventually terminated, then the next ASG group tried or if only one group, to try again

What happened instead?:

The timed out EC2 instance came up eventually and stayed running for > 8 hours (GPU node$$)
No other nodes were scaled up and our processing pipeline was effectively paused
There were no errors logged in AWS ASG activity history
The only errors were logged by cluster-autoscaler including a million "Failed to find readiness information"

How to reproduce it (as minimally and precisely as possible):

I'd bet you could reproduce it quickly by setting max-node-provision-time to 1m (if that is possible)

Anything else we need to know?:

This was already filed here #3490 for the same company's cluster 4 years ago. That was about a spot instance, this is about a GPU instance

@charlesritchea charlesritchea added the kind/bug Categorizes issue or PR as related to a bug. label May 9, 2024
@charlesritchea
Copy link
Author

I just reverted the max-node-provision-time to the default to resolve this, but if there is a minimum max-node-provision-time that actually works it should be documented and enforced

@adrianmoisey
Copy link
Member

/area cluster-autoscaler

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster-autoscaler kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants