[MCOL-1500] Columnstore configuration file left in a bad state after user enables local query, then disable feature Created: 2018-06-25 Updated: 2020-08-25 Resolved: 2019-07-10 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.1.5 |
| Fix Version/s: | 1.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
A customer reported an issue with memory over usage and the system restarting due to pm2 swapping. Issue was the exemgr was incorrectly running on pm2 and utilizing memory. Jun 22 10:27:25 usfit-scdocker2 ServerMonitor[10835]: 25.593968 |0|0|0| I 09 CAL0000: Memory Usage for Process: PrimProc : Memory Used 4011534 : % Used 31 The problem turned out to be that the user configured the system with 'local query' feature enabled which added additional exemgr entries in the Columnstore.xml. But then they ran postConfigure again and selected disable of the 'local query' feature, but the entroes didnt get removed from the COlumnstore.xml this from a system that had 1um and 2 pm <ExeMgr2> |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2019-07-10 ] |
|
In later versions this will not be an issue. In the mean time a user should not try to do this. |