Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
1.4.2
-
None
-
SkySQL - mariadb/skysql-columnstore:1.4.2-2-SKIP-OAM
Description
Executing `columnstoreDBWrite -c suspend` to a ColumnStore system which is still executing writes doesn't succeed. The return code of the program further doesn't indicate the failure.
[root@dbaas-1633-mdb-cs-single-0 /]# columnstoreDBWrite -c suspend |
The following tables are locked:
|
LockID Name Process PID Session CreationTime State DBRoots
|
10 test.tmp2 cpimport 4414 BulkLoad 2020-02-17 01:33:37 PM LOADING 1 |
[root@dbaas-1633-mdb-cs-single-0 /]# echo $? |
0
|
It would be better if `columnstoreDBWrite -c suspend` either
- forces the write only mode (by killing the active queries), or if it
- blocks all further write queries, waits until the active write queries are finished, and then puts ColumnStore into read only mode.
In case of an error, I would further expect a return code unequal to 0.