-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Consul consumes tens GB or RAM for no reason #16290
Comments
@AndreiPashkin , could you provide more info about how the distributed locks and |
Hello, we've faced with the similar problem, Consul servers consumes all of dedicated RAM gradually. After that, rebooted and work normally 3-4 days. The consul has been working fine for the last six days. Total load decreased and consul stopped to consume all of the dedicated RAM. I've tried to analyze it with consul-snapshot-tool, but there was nothing special as in related issue - #5327 (comment) |
Hello, we've gathered some metrics, hope it'll help with analyze |
@huikang, I've captured logs using |
Overview of the Issue
We use Consul in single-node mode for distributed locks and for service-discovery in our app. Service discovery used to connect our application environments with our monitoring. Consuls connect with each other over WAN.
After startup it starts consuming memory very quickly, memory usage goes over 30GB and quickly overwhelms our server. What I've found is that repeated calls to
consul info
shows thatgoroutines
number increases rapidly along with increase of memory usage.I'm also attaching logs.
I cap provide
consul debug
output by request of maintainers.Possibly related issues: #12564, #9076, #12288, #3111
Reproduction Steps
So far I haven't figure out how to reproduce it in isolated environment.
Consul info for both Client and Server
Server info
Operating system and Environment details
Ubuntu 20.04
Log Fragments
https://gist.github.com/AndreiPashkin/0a95cdcb5e349c881ff4ee94af5f7b15
Version
The text was updated successfully, but these errors were encountered: