[MCOL-1115]  An unexpected condition within the query caused an internal processing error within InfiniDB. Please check the log files for more details. Additional Information: error in BatchPrimitiveProces Created: 2017-12-15  Updated: 2021-01-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: hiller1 Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

columnstore 1.0.11



 Description   

查询:select id,update_time from streaming_customer_info limit 10

错误代码: 1815
Internal error: An unexpected condition within the query caused an internal processing error within InfiniDB. Please check the log files for more details. Additional Information: error in BatchPrimitiveProces

-------------------------------
schema
-----------------------------
CREATE TABLE `streaming_customer_info` (
`id` bigint(20) DEFAULT NULL ,
`create_time` datetime DEFAULT NULL ,
`update_time` datetime DEFAULT NULL ,
`work_id` bigint(20) DEFAULT NULL ,
`name` varchar(64) DEFAULT NULL ,
`id_no` varchar(128) DEFAULT NULL ,
`register_mobile` varchar(255) DEFAULT NULL ,
`age` int(11) DEFAULT NULL ,
`education` int(11) DEFAULT NULL ,
`salary` varchar(16) DEFAULT NULL ,
`entry_month_count` int(11) DEFAULT NULL ,
`house` int(11) DEFAULT NULL ,
`married` int(11) DEFAULT NULL ,
`children` int(11) DEFAULT NULL ,
`register_email` varchar(256) DEFAULT NULL ,
`register_qq` varchar(16) DEFAULT NULL ,
`company_mobile` varchar(255) DEFAULT NULL,
`bind_bank_no` varchar(128) DEFAULT NULL ,
`bind_bank_mobile` varchar(255) DEFAULT NULL ,
`relative_mobile_1` varchar(255) DEFAULT NULL ,
`relative_mobile_2` varchar(255) DEFAULT NULL,
`relative_mobile_3` varchar(255) DEFAULT NULL,
`mac_id` varchar(64) DEFAULT NULL,
`user_day_login_count` int(11) DEFAULT NULL,
`user_hour_login_count` int(11) DEFAULT NULL,
`user_login_count` int(11) DEFAULT NULL,
`bind_bank_fail_count` int(11) DEFAULT NULL,
`buy_num_flag` varchar(32) DEFAULT NULL,
`student_score` int(11) DEFAULT '300',
`job` int(11) DEFAULT NULL,
`is_true_count` int(11) DEFAULT NULL,
`gender` tinyint(4) DEFAULT NULL,
`city_code` int(11) DEFAULT NULL,
`photo_json_info` varchar(1000) DEFAULT NULL
) ENGINE=Columnstore DEFAULT CHARSET=utf8;
---------------------------------------------------------------------------



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2017-12-15 ]

This typically happens if the extent files cannot be opened for some reason, but there are other potential causes. Can you please generate a support report for this so we can see further details on the error?:

https://mariadb.com/kb/en/library/system-troubleshooting-mariadb-columnstore/#mariadb-columnstore-support-report-tool

Comment by David Thompson (Inactive) [ 2017-12-15 ]

hi @hiller1, can you check the logs under /var/log/mariadb/columnstore. There isn't enough information here for us to triage or reproduce. If the error is not obvious can you add the logs here or preferably a columnstore support report?

Comment by hiller1 [ 2017-12-18 ]

I drop this table and recreated it, just fine

HI,I have uploaded ftp://ftp.mariadb.com/uploads/

the file name is columnstoreSupportReport.MPP_multi-node separate_hiller.tar.gz

thanks!

Comment by David Thompson (Inactive) [ 2017-12-19 ]

Thanks, is the issue resolved now? If not when exactly did the reported problem occur? In some of the older err.log files under archive i see the following entry:
Dec 7 00:31:32 um1 dmlpackageproc[49086]: 32.434169 |0|0|0| E 21 CAL0001: Insert Failed: no space for a dictionary insert

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