[MCOL-4104] If ColumnStore services are not running, then statements return unhelpful "Cannot execute the statement. DBRM is read only!" error message Created: 2020-06-24  Updated: 2023-10-27  Resolved: 2023-10-27

Status: Closed
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: 1.5.2
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Leonid Fedorov
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-4093 "mysqld --bootstrap" / mysql_install_... Closed

 Description   

If you stop the ColumnStore services:

$ sudo systemctl stop mariadb-columnstore

Then operations fail with an unhelpful error message:

MariaDB [(none)]> CREATE TABLE columnstore_db.tab2 (id INT) ENGINE=ColumnStore;
 
ERROR 1815 (HY000): Internal error: Cannot execute the statement. DBRM is read only!

It would be more user friendly to print some kind of message like this instead:

ERROR: 1815  Internal error: Cannot communicate with MariaDB ColumnStore processes. Check the status of the processes by executing "systemctl status mariadb-columnstore."

MCOL-4093 is similar, but it is about the effect on mysql_install_db.

 Comments   
Comment by Gregory Dorman (Inactive) [ 2020-06-25 ]

David - please dispatch this to whoever needs to fix it. And talk to toddstoffel about whether this can be made available to customers and community now, or only in the next release, etc.

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