[MCOL-3889] Plug storagemanager config file into build system Created: 2020-03-16  Updated: 2020-12-10  Resolved: 2020-12-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: Storage Manager
Affects Version/s: 1.4.3, 1.5.3
Fix Version/s: 5.5.1

Type: Task Priority: Minor
Reporter: Patrick LeBlanc (Inactive) Assignee: Ben Thompson (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Epic Link: ColumnStore S3 Improvements

 Description   

The storagemanager.cnf still has the default for its storage at $HOME/storagemanager. That should be parameterized, and generated by cmake. For default installations it should be /var/lib/columnstore/storagemanager.

Upgrades shouldn't be affected because we currently copy their old configuration to their new configuration. Presumably, whatever they are currently using is fine with them.

 Comments   
Comment by Patrick LeBlanc (Inactive) [ 2020-04-22 ]

I changed the ${HOME}'s to /var/lib/columnstore to make sure the most important part of this got done before the next release.

Comment by Ben Thompson (Inactive) [ 2020-12-03 ]

Changing this to storagemanager.cnf.in and use the existing CMAKE value for ENGINE_DATADIR "/var/lib/columnstore"

Comment by Daniel Lee (Inactive) [ 2020-12-09 ]

Build tested: 5.5.1 (Drone #1302 centos 8, #1304 ubuntui18.04)

After installation, the single-node cluster is in DBRM ready only state.
When trying to create a table, the following error returned:

ERROR 1815 (HY000) at line 7: Internal error: Cannot execute the statement. DBRM is read only!

crit.log

Dec 9 18:00:39 centos-8 controllernode[3268]: 39.401421 |0|0|0| C 29 CAL0000: OIDServer::readData(): read error: iostream error... attempt #1/10 to restart the DBRM controller node
Dec 9 18:00:47 centos-8 DMLProc[3357]: 47.633933 |0|0|0| C 20 CAL0002: DMLProc failed to start due to : Rollback will be deferred due to DBRM is in read only state.
Dec 9 18:00:47 centos-8 ddlpackageproc[3353]: 47.634929 |0|0|0| C 23 CAL0008: DMLProc main process initialization failed
Dec 9 18:00:49 centos-8 ddlpackageproc[3363]: 49.745551 |0|0|0| C 23 CAL0008: DDLProc main process has started
Dec 9 18:01:11 centos-8 controllernode[3321]: 11.698194 |0|0|0| C 29 CAL0000: Couldn't create oid bitmap file /var/lib/columnstore/data1/systemFiles/dbrm/oidbitmap: Connection refused
Dec 9 18:01:11 centos-8 controllernode[3321]: 11.698555 |0|0|0| C 29 CAL0000: Couldn't create oid bitmap file /var/lib/columnstore/data1/systemFiles/dbrm/oidbitmap: Connection refused: iostream error... attempt #1/10 to restart the DBRM controller node
Dec 9 18:01:44 centos-8 controllernode[3321]: 44.167833 |0|0|0| C 29 CAL0000: Couldn't create oid bitmap file /var/lib/columnstore/data1/systemFiles/dbrm/oidbitmap: Connection refused
Dec 9 18:01:44 centos-8 controllernode[3321]: 44.168169 |0|0|0| C 29 CAL0000: Couldn't create oid bitmap file /var/lib/columnstore/data1/systemFiles/dbrm/oidbitmap: Connection refused: iostream error... attempt #2/10 to restart the DBRM controller node
Dec 9 18:02:05 centos-8 writeengine[3381]: 05.524942 |0|0|0| C 19 CAL0060: dbbuilder system catalog error: Creating TableName column OID: 1001 a BRM Allocate extent error. [BRM error status: network error]
Dec 9 18:02:14 centos-8 controllernode[3321]: 14.882017 |0|0|0| C 29 CAL0000: Couldn't create oid bitmap file /var/lib/columnstore/data1/systemFiles/dbrm/oidbitmap: Connection refused

The same installation with MCS_USE_S3_STORAGE=0 worked fine.
The same installation with MCS_USE_S3_STORAGE=1 on release 5.4.3-1 worked fine.

Comment by Daniel Lee (Inactive) [ 2020-12-10 ]

The requested change of this ticket has been completed. The identified issue is not related to this ticket and it is being tracked by MCOL-4437.

Generated at Thu Feb 08 02:46:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.