Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.2
-
None
-
None
-
2021-9, 2021-10
Description
- It occurs on some tables, but no others (flights, but not airlines)
- Sometimes it blows up on limit1, sometimes on limit 2, sometimes on 10, sometimes on 10000
- Errors vary. In case of dockers the cluster is hosed and requires recycling (on prem systemd repairs it).
- Verified in 5.5.2 and 5.6.1
To reproduce:
Starting with the flights sample data (bts):
https://github.com/mariadb-corporation/mariadb-columnstore-samples
MariaDB [bts]> create table test as select *, md5(rand(1)) from flights; |
ERROR 1815 (HY000): Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() IDB-2035: An internal error occurred. Check the error log file & contact support |
|
|
MariaDB [gjd]> use bts
|
Database changed
|
MariaDB [bts]> select rand() from flights limit 1; |
+---------------------+
|
| rand() |
|
+---------------------+
|
| 0.06580742547829396 | |
+---------------------+
|
1 row in set (0.118 sec) |
|
|
MariaDB [bts]> select rand() from flights limit 2; |
ERROR 1815 (HY000): Internal error: TupleBPS::run() caught DistributedEngineComm::write: Broken Pipe error |
MariaDB [bts]>
|
MariaDB [bts]> create table test as select *, md5(rand(1)) from flights; |
ERROR 1815 (HY000): Internal error: IDB-2045: At least one PrimProc closed the connection unexpectedly. |
Attachments
Issue Links
- is duplicated by
-
MCOL-4487 ORDER BY RAND() ERROR 1815 (HY000): Internal error: IDB-2045: At least one PrimProc closed the connection unexpectedly.
-
- Closed
-