The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.

hi when i loading data to mariadb columnstore and at the same time run query :select max(create_time) from tr_table; get error : ERROR 1815 (HY000): Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support. in error.log have the message: > offset' failed Feb 7 10:04:27 db03 PrimProc[12878]: 27.287345 |0|0|0| C 28 CAL0000: std::bad_alloc Feb 7 10:04:27 db03 joblist[12925]: 27.370566 |19|0|0| C 05 CAL0000: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support. Feb 7 10:04:27 db03 PrimProc[12878]: 27.430876 |0|0|0| C 28 CAL0000: std::bad_alloc Feb 7 10:07:33 db03 threadpool[12925]: 33.022445 |0|0|0| E 22 CAL0005: ThreadPool: Caught exception during execution: std::bad_alloc Feb 7 10:07:33 db03 threadpool[12925]: 33.022452 |0|0|0| E 22 CAL0005: ThreadPool: Caught exception during execution: std::bad_alloc Feb 7 10:07:33 db03 ProcessMonitor[12225]: 33.451858 |0|0|0| C 18 CAL0000: *Calpont Process Restarting: ExeMgr, old PID = 12925 Feb 7 10:07:45 db03 ProcMon[12225]: 45.464664 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:08:09 db03 joblist[12635]: 09.287427 |0|0|0| C 05 CAL0000: /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 318 Could not get a ExeMgr connection. Feb 7 10:08:10 db03 joblist[12635]: 10.356032 |0|0|0| C 05 CAL0000: /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 318 Could not get a ExeMgr connection. Feb 7 10:14:45 db03 ProcessMonitor[12225]: 45.062080 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:14:57 db03 ProcessMonitor[12225]: 57.841166 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:00 db03 ProcessMonitor[12225]: 00.064028 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:11 db03 ProcessMonitor[12225]: 11.625719 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:12 db03 ProcessMonitor[12225]: 12.856489 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:15 db03 ProcessMonitor[12225]: 15.079342 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:19 db03 ProcessMonitor[12225]: 19.653406 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:21 db03 ProcessMonitor[12225]: 21.646879 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:27 db03 ProcessMonitor[12225]: 27.859828 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:40 db03 ProcessMonitor[12225]: 40.093307 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:41 db03 ProcessMonitor[12225]: 41.627652 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:42 db03 ProcessMonitor[12225]: 42.861542 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 Feb 7 10:15:49 db03 ProcessMonitor[12225]: 49.655140 |0|0|0| E 18 CAL0000: messagethread: pthread_create failed, return status = 11 run statement: mcsadmin getSystemInfo printSystemStatus Failed = API Failure return in getSystemStatus:MessageQueueClient-Error API then run query:select max(create_time) from tr_table; get error:ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.

Answer Answered by David Thompson in this comment.

without having more details (perhaps file a jira with a columnstore support report) i'd suspect that the combination of the cpimport and query is causing the memory to go into heavy swap leading to the system restarting exemgr which causes this type of error.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.