[MCOL-2068] add support for using and defaulting memory based settings to docker image Created: 2019-01-07 Updated: 2019-04-03 Resolved: 2019-04-03 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | Docker |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | 1.2.4 |
| Type: | Task | Priority: | Major |
| Reporter: | David Thompson (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | containers, relnote | ||
| Issue Links: |
|
||||||||
| Sprint: | 2018-21, 2019-01, 2019-02, 2019-03 | ||||||||
| Description |
|
ColumnsStore now supports explicit memory settings for NumBlocksPct and TotalUmMemory however i believe there is not currently a way to force / override these in postConfigure. The docker image should support 2 new env variables to allow overriding these and also default to some sensible small values like 1024m for NPB and 512m for TUM. Assuming my analysis is correct we'll need a mechanism to allow postCfg to take and default values for these (either as parameters or utilizing the values already in ColumnStore.xml (there is some logic for this in the upgrade path). |
| Comments |
| Comment by Jens Röwekamp (Inactive) [ 2019-01-17 ] |
|
Added command line parameter to postConfigure to set the Columnstore.xml values
Further created a new branch develop-1.2 in mariadb-columnstore-docker that uses the yum repository build from the Columnstore 1.2.3 (develop-1.2) branches. Added and documented the necessary environment variables and code in mariadb-columnstore-docker to set this values through the initial dbinit script. Note: The develop-1.2 mariadb-columnstore-docker repository can only be used and verified once the changes to mariadb-columnstore-engine are applied and the new packages are build by buildbot and uploaded to nightly. In the meantime one could use the yum repository: For QA:
|
| Comment by Daniel Lee (Inactive) [ 2019-04-03 ] |
|
Build verified: 1.2.4-1 nightly server commit: 1. Verified postConfigure help text |