[MDEV-14260] Memory leak in mysqld - needs restart every week Created: 2017-11-02 Updated: 2018-05-30 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.1.25, 10.1.26, 10.1.28 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | sjon | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | memory, server | ||
| Environment: |
linux x86_64 |
||
| Attachments: |
|
| Description |
|
Since upgrading to 10.1.25 we've had major problems with memory usage on our mariadb server. Unfortunately this is hard to debug and I'm not sure what causes this. Mysql will get killed by our OOM killer (which never happened before this version): Killed process 1404 (mysqld) total-vm:7122540kB, anon-rss:1915704kB, file-rss:0kB, shmem-rss:0kB
While using this large amounts of memory, kill -HUP reports:
I'm attaching our cacti-graph to illustrate the issue - you can clearly see the various releases mixed with restarts and OOM kills. Mysql itself doesn't report the usage so I think it is leaking somewhere. |
| Comments |
| Comment by Elena Stepanova [ 2018-05-30 ] |
|
Hi, Are you still experiencing the problem, and if so, which version are you using now? There have been several fixes for memory leaks or unnecessary consumption after 10.1.28 (last version that you indicated as affected), it just might happen that one of them will fix your case, too. |
| Comment by sjon [ 2018-05-30 ] |
|
actually one of those releases did indeed fix this issue. Could you point me towards these issues or documentation so I can find these sort of memleaks in the future? |