Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.25, 6.2.1, 22.08.5, 23.02.0, 23.02.1
-
Running in a VM - Ubuntu 20.04.6 LTS, 2 CPUs, 4GB RAM (8GB for production)
-
MXS-SPRINT-181, MXS-SPRINT-182
Description
The memory usage of MaxScale keeps growing and eventually swap is used and then MaxScale gets busted one night (or day).
Issue observed on our pre-prod MaxScale - version 23.02.1. The same observed in prod (6.2.1). Currently, holding prod upgrade.
Stack trace has been logged (attached). Next step is using jemalloc to profile the heap as Markus suggested.
Attachments
Issue Links
- relates to
-
MXS-4582 Maxscale crash with OOM
- Closed