[MCOL-2216] add support for modifying DBRoot during post-install Created: 2019-03-06 Updated: 2020-01-16 Resolved: 2020-01-16 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | Docker |
| Affects Version/s: | 1.2.3 |
| Fix Version/s: | 1.2.6 |
| Type: | Task | Priority: | Major |
| Reporter: | Alexander Aldev (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | containers | ||
| 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). |
| Comments |
| Comment by Alexander Aldev (Inactive) [ 2019-03-06 ] |
|
In versions <= 1.2.3, we are using a workaround where an empty PV is provisioned, the contents of /usr/local/mariadb/columnstore copied to it on first start (using an initContainer) and then the PV mounted under /usr/local/mariadb/columnstore. This operation, however, is quite slow. |