Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Product
- alter table engine=columnstore
We should stop/warn customer if trying to run on a table > 500 rows, else it takes an eternity or make it actually performant
https://jira.mariadb.org/browse/MCOL-5907
- Backups / Restore ( physical and logical )
cmapi wrapper of backup/restore not done, much less public facing docs on how to run
cmapi even for single nodes
- columnstore doesnt warn or have a dependancy for the cmapi package, even though you need it since 23.02.4+, prospect was using without cmapi for a month+
unclear mariadb-columnstore systemd unit masking, cant start columnstore once cmapi installed but not configured, leading customer to think someone is wrong but not what ERROR 1815 (HY000) : Internal error: DBRM is not responding. Cannot accent queries
- mcsRebuildEM not working
Rebuild EM:rw-rr- 1 root root 1080428 Oct 24 12:13 BRM_saves_em - why does it even leave it owned by root, and its size is almost double that the original
Prior EM from october 18th:rw-rr- 1 mysql mysql 585260 Oct 18 10:06 BRM_saves_em
resulting in error AL0000: Invalid Range from HWM for lbid 37924864, range size should be <= blocksReadAhead: HWM 0, dbroot 1, highfbo 10751, lowfbo 10240, blocksReadAhead 512, range size -10239#012 %%10%% after startup and trying to query using the rebuilt em
Attachments
Issue Links
- relates to
-
MCOL-5877 New User Experience Challenges
-
- Closed
-