Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
6.4.2, 6.4.4
-
None
-
Debian OS 11.3
-
MXS-SPRINT-171, MXS-SPRINT-172, MXS-SPRINT-173, MXS-SPRINT-174, MXS-SPRINT-179, MXS-SPRINT-180, MXS-SPRINT-181, MXS-SPRINT-182, MXS-SPRINT-183, MXS-SPRINT-204, MXS-SPRINT-205, MXS-SPRINT-206, MXS-SPRINT-207, MXS-SPRINT-208
Description
Hi Team,
We see a linear increase of ram usage, finally crashing maxscale at 100% ram usage..
The maxscale process was killed by the oom_killer.. Here I have attached the maxsclae config file and memory usage graphs.. Please check it..
Attachments
Issue Links
- split to
-
MXS-5103 query_classifier_cache_size=0 with short connections appears to leak memory
-
- Closed
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
12d 14h 54m | 1 |
|
48d 2h 59m | 1 |
|
20d 23h 24m | 1 |
|
48d 17h 25m | 1 |
|
9h 6m | 2 |
|
254d 20h 31m | 1 |
|
110d 2h 56m | 1 |
|
54d 18h 45m | 1 |