[MCOL-3923] Modify existing MCS packages rules. Created: 2020-04-03 Updated: 2021-01-25 Resolved: 2020-09-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Roman | Assignee: | Roman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
At this point there will be no need to run columnstore-post-install or postConfigure manually and by default installation provides a user with a single-node installation. |
| Comments |
| Comment by Patrick LeBlanc (Inactive) [ 2020-06-22 ] |
|
Normally configuring cgroups is something a sysadmin would do. What kind of cgroup rules are you thinking about? |
| Comment by Roman [ 2020-06-23 ] |
|
How would you limit RAM consumption for a group of processes w/o writing complicated mechanism on top of shared memory? This is one of the cgroups application and that is why we want them as part of our package, namely to put an overall RAM consumption limit for WE,PP and ExeMgr allowing them to utilize up to 100% of allowed quota. Why do we need this? Now our primary node will be both PM and UM and we can't set RAM limits in the xml that will be good enough for such mixed workload. Moreover if one makes specific primary node settings to prioritise ExeMgr over other processes then with primary role migration one needs to move the settings to another node. |