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

[Port v2.9] cluster deploy running excessively and taking a long time to execute #44924

Closed
moio opened this issue Mar 26, 2024 · 1 comment
Closed
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Milestone

Comments

@moio
Copy link
Contributor

moio commented Mar 26, 2024

This is a port of #39597

Rancher Server Setup

  • Rancher version: 2.9.x
  • Installation option: any
  • Proxy/Cert Details: irrelevant

Information about the Cluster

  • Kubernetes version: irrelevant
  • Cluster Type (Local/Downstream): issue is seen in local cluster with at least one disconnected cluster

User Information

  • What is the role of the user logged in? irrelevant

Describe the bug
With a disconnected downstream cluster, the clusterdeploy handler takes several seconds to time out. This is fine with only a few downstream clusters disconnected, but when the number of disconnected clusters goes over 50 or so, the worker queues will get saturated.

Reason for the slow time out is that the handler may execute code that reaches out to the disconnected downstream cluster - typically clusterDeploy.getNodeAgentImage which tries to list DaemonSets. That alone can take up to ~30 seconds due to how TunnelServer's remotedialer mechanism works.

To Reproduce
See #39597 (comment)

Result

Expected Result
Little to no executions of cluster deploy handler while creating users. Cluster deploy handler should not probably not exceed an execution time of 1 second.

Screenshots
N/A
Additional context
N/A

@moio moio added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Mar 26, 2024
@moio moio added this to the v2.9-Next1 milestone Apr 8, 2024
@moio
Copy link
Contributor Author

moio commented Apr 24, 2024

closing per conversation with @git-ival

@moio moio closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

1 participant