- Clone repository
- Make sure
docker
anddocker-compose
are installed on the system cd haproxy-memory-leak
- Start containers
docker-compose up --build
- Open Grafana on http://localhost:3000/
- There are two dashboards -
HAProxy 2 Full
(all HAProxy metrics) andDocker Containers
- Open
Docker Containers
dashboard in Grafana, scroll toContainer Memory Usage
widget - Pick
haproxy23
andhaproxy24
containers - Observe that
haproxy24
container does not free memory - Stop containers
docker-compose down
- Comment lines 18-21 and 4 in
application/main.go
(do not return HTTP 500 errors) - Repeat test
- Observe that now
haproxy24
maintains memory correctly
This repository has been archived by the owner on Dec 18, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
danielleontiev/haproxy-memory-leak
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
Demo of possible HAProxy memory leak for bug-report