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

Bug: Memory Increasing Gradually and Not GCing #4883

Closed
2 tasks done
kripanshdevtron opened this issue Apr 4, 2024 · 0 comments · Fixed by #4909
Closed
2 tasks done

Bug: Memory Increasing Gradually and Not GCing #4883

kripanshdevtron opened this issue Apr 4, 2024 · 0 comments · Fixed by #4909
Assignees
Labels
bug Something isn't working

Comments

@kripanshdevtron
Copy link
Contributor

📜 Description

It has been observed, Orchestrator memory is getting increased gradually on daily basis, and after a few days it gets OOMKilled.

👟 Reproduction steps

1.) Use Cluster Terminal and put it in dangling state
2.) Fetch Ingress URLs

👍 Expected behavior

Memory should get GCed when objects getting freed.

👎 Actual Behavior

After 10-15 days Orchestrator gets OOMKilled

☸ Kubernetes version

EKS 1.23

Cloud provider

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants