[MDEV-17758] Query to INFORMATION_SCHEMA.TABLES leads to huge memory usage Created: 2018-11-17 Updated: 2019-01-27 Resolved: 2019-01-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.2.19 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Igor Blinder | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
OC: Cloulinux/CentOS 7.5 |
||
| Attachments: |
|
| Description |
|
The bug similar to https://bugs.launchpad.net/percona-server/+bug/1380895 Sometimes after execution requests to INFORMATION_SCHEMA.TABLES mysql use more and more memory.
Memory usage before request. pmap out before request in attach before_pmap.log
Execution request. Memory usage after request. pmap out after request in attach after_pmap.log
Increasing of memory usage happens not every request. |
| Comments |
| Comment by Elena Stepanova [ 2018-12-29 ] |
|
The query from information_schema opens a lot of tables – all tables, in fact – so it doesn't appear surprising that it might use some memory. The question is, whether there is a leak, whether the growth continues over the time, and whether it growth beyond what you'd expect if the number of tables also increases. I don't see in your report any indication of one way or another, so could you please clarify, do you observe a leak? |