[MCOL-1311] Memory leak in PrimProc is followed by restarting of MCS system in the occurrence of next memory processing on PM(s) Created: 2018-03-28 Updated: 2018-04-11 Resolved: 2018-04-09 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | PrimProc |
| Affects Version/s: | 1.1.3 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Zdravelina Sokolovska (Inactive) | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS 7.4 |
||
| Description |
|
Memory leak in PrimProc is followed by restarting of MCS system in the occurrence of next memory processing on PM(s) PrimProc process does not deliberate the used memory and it appears it's observed memory leak in the PrimProc process on PM(s) Nodes The problem with restarting MCS appears when other more memory consuming processes For example : how to repeat : note: at appears that the ExeMgr on UM also gets more memory during some query processing --more than 50% , but it's returned back and finally test finished with 2-3% in ExeMgr
|
| Comments |
| Comment by David Hall (Inactive) [ 2018-03-28 ] |
|
PrimProc uses (by default) 70% of memory for cache. Cache is not released (or it wouldn't be cache). |
| Comment by Andrew Hutchings (Inactive) [ 2018-04-09 ] |
|
As David mentioned this is normal usage for PrimProc as it needs it for a block cache which fills as queries are being processed until it hits the ceiling (70% by default) and then manages itself to stop growing (an LRU cache). The usage is pretty much spot on the expected amount. ExeMgr uses the memory for joins and aggregates so that memory is freed after every query. Closing this as !Bug |