[MCOL-580] Got Internal error: IDB-2004: Cannot connect to ExeMgr. when run query Created: 2017-02-22  Updated: 2017-05-08  Resolved: 2017-05-08

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 1.0.7
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: john dolphin Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

Ubuntu


Attachments: File info.log     Text File pm1_resourceReport.txt     File temp-db-ubuntu.err    

 Description   

Got Internal error: IDB-2004: Cannot connect to ExeMgr. when run query
select record_id,count from record where record_time>='2017-02-18 00:00:00' and record_time<'2017-02-19 00:00:00' group by record_id having count>1;

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2017-02-22 ]

We are figuring out a solution to attach your logs, I've attached some important ones for now. In the mean time the reason you are getting this error is that your RAM and swap space are maxxed out so PrimProc and ExeMgr are getting restarted.

If you look at around 10:27/10:28 on the info and err logs attached you will see what I mean.

Comment by David Hill (Inactive) [ 2017-02-22 ]

Can you let us know what these 2 memory settings are by running the following commands:

  1. /usr/local/mariadb/columnstore/bin/getConfig HashJoin TotalUmMemory
  2. /usr/local/mariadb/columnstore/bin/getConfig DBBC NumBlocksPct

Thanks

Comment by David Hill (Inactive) [ 2017-02-22 ]

also please provide a copy or cat your my.cnf file... We would like to see what settings are in there related to memory that could be causing the system to using over 100% of memory.

Thanks

Comment by David Thompson (Inactive) [ 2017-05-08 ]

Please re-open if you can reproduce this still and provide requested info.

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