Details
-
Bug
-
Status: In Review (View Workflow)
-
Critical
-
Resolution: Unresolved
-
22.08.4
-
None
-
2023-12, 2024-1
Description
Build tested: 22.08.4, as well as the latest in develop
engine: 15f65eff157f8fce48c0dfb30548dc787b259eb2
server: d3049350bb5c61340f5a7518b155d3c9dacdcb33
buildNo: 6257
The TRUNCATE command fails after PrimProc is restarted on single-node setup,
or on the primary node of a multi-node cluster. If PrimProc was restarted on slave node, TRUNCATE would still succeed.
MariaDB [mytest]> truncate lineitem;
|
ERROR 1815 (HY000): Internal error: CAL0009: Truncate table failed: MCS-2045: At least one PrimProc closed the connection unexpectedly.
|
Repeating the TRUNCATE command would continue to return error, unless a create table command has been processed.
MariaDB [mytest]> truncate lineitem;
|
ERROR 1815 (HY000): Internal error: CAL0009: Truncate table failed: MCS-2045: At least one PrimProc closed the connection unexpectedly.
|
MariaDB [mytest]> create table t1 (c1 int) engine=columnstore;
|
Query OK, 0 rows affected (0.085 sec)
|
 |
MariaDB [mytest]> truncate lineitem;
|
Query OK, 0 rows affected (0.089 sec)
|
