Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
1.2.3
Description
The DBRoot directory seems to be hardcoded to /usr/local/mariadb/columnstore in postConfigure.cpp.
When running CS in containers, data directories only (which are sub-directories of said path) need to be mapped to a persistent volume, while binaries etc continue to remain in an ephemeral volume under this directory.
I would like to request that the DBRoot is added as a parameter to postCfg (assuming only data directories will be hosted under it).
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | CLONE - add support for using and defaulting memory based settings to docker image | add support for modifying DBRoot during post-install |
| Affects Version/s | 1.2.3 [ 23231 ] | |
| Affects Version/s | 1.2.2 [ 23220 ] |
| Labels | containers relnote | containers |
| 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). |
The DBRoot directory seems to be hardcoded to /usr/local/mariadb/columnstore in the post. When running in containers, data directories only (which are sub-directories of said path) need to be mapped to a persistent volume, while binaries etc continue to remain in an ephemeral volume under this directory.
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). |
| Description |
The DBRoot directory seems to be hardcoded to /usr/local/mariadb/columnstore in the post. When running in containers, data directories only (which are sub-directories of said path) need to be mapped to a persistent volume, while binaries etc continue to remain in an ephemeral volume under this directory.
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). |
The DBRoot directory seems to be hardcoded to /usr/local/mariadb/columnstore in postConfigure.cpp.
When running CS in containers, data directories only (which are sub-directories of said path) need to be mapped to a persistent volume, while binaries etc continue to remain in an ephemeral volume under this directory. I would like to request that the DBRoot is added as a parameter to postCfg (assuming only data directories will be hosted under it). |
| Fix Version/s | 1.2.4 [ 23254 ] | |
| Fix Version/s | 1.2.3 [ 23231 ] |
| Fix Version/s | 1.2.5 [ 23613 ] | |
| Fix Version/s | 1.2.4 [ 23254 ] |
| Assignee | David Thompson [ dthompson ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Fix Version/s | 1.2.6 [ 23734 ] | |
| Fix Version/s | 1.2.5 [ 23613 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |