Memory Leak With consul client
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Overview of the Issue
We use Consul with Haproxy and the consul client sometimes eats all the memory in the server and gets killed due to Out Of memory.


#### Reproduction Steps
It usually happens when we restart the consul client.
### Consul info for both Client and Server
Client info
We use the latest consul client (1.11.4)
Server info
Consul v1.10.2
Revision 3cb6eeedb
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
### Operating system and Environment details
We use Centos 7
### Log Fragments
[consul-debug-2022-03-16T11-15-39+0700.tar.gz](https://github.com/hashicorp/consul/files/8259017/consul-debug-2022-03-16T11-15-39%2B0700.tar.gz)
Contributor guide
Research direction
Start by reviewing the attached Consul debug archive and reproducing the issue while restarting the Consul client. Trace the memory growth and verify that repeated restarts no longer cause unbounded memory use or an out-of-memory kill.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100