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

istio-discovery container is taking up large amounts of memory or leaking memory #1

Open
alyssa-tc opened this issue Jun 14, 2019 · 2 comments

Comments

@alyssa-tc
Copy link

I installed this on our cluster EKS K8S 1.11, and I noticed the istio-discover container using up large amounts of memory - approximately 20GB. Please look into this. It may be a memory leak

@dorkolog
Copy link
Collaborator

hi @alyssa-tc

I just run a cluster with >1000 ServiceEntires created sequentially (simple loop running curl)
dns-discovery was hitting 22mb-26mb res mem, so I wasn't able to reproduce this leak.

Can you please elaborate more about your environment, use-case, # serviceentries created - and anything else that might help me to spot this issue ?

@alyssa-tc
Copy link
Author

We have 202 service entries. Use case is to do what dns-discovery is meant for- finding DNS names for all outbound traffic. We had it enabled for a few days before . See datadog screenshot. We have limits set in k8s so the container gets killed when memory usage goes too high.

Screen Shot 2019-06-17 at 10 21 18 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants