[MCOL-3509] S3 Select count(*) one 100g line item returned a compression error Created: 2019-09-17  Updated: 2019-10-11  Resolved: 2019-10-11

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

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Build tested: 1.2.5-1 with S3, a special build

Using S3 localStorage, I create a dbt3 database and cpimported 100g dataset. Select count from lineitem returned compression errors:

The same test worked fine on 1.4.0-1

MariaDB [tpch100]> select count from lineitem;
ERROR 1815 (HY000): Internal error: An unexpected condition within the query caused an internal processing error within Columnstore. Please check the log files for more details. Additional Information: error in BatchPrimitivePro

From err.log
Sep 13 21:09:10 localhost PrimProc[9212]: 10.276634 |0|0|0| C 28 CAL0061: PrimProc error reading file for OID 6164; Error decompressing block 1 code=-1 part=8 seg=0
Sep 13 21:09:10 localhost PrimProc[9212]: 10.280727 |0|0|0| C 28 CAL0061: PrimProc error reading file for OID 6164; Error decompressing block 1 code=-1 part=8 seg=0
Sep 13 21:09:13 localhost PrimProc[9212]: 13.094637 |0|0|0| C 28 CAL0061: PrimProc error reading file for OID 6164; Error decompressing block 1 code=-1 part=8 seg=0
Sep 13 21:09:15 localhost PrimProc[9212]: 15.665172 |0|0|0| C 28 CAL0061: PrimProc error reading file for OID 6164; Error decompressing block 1 code=-1 part=8 seg=0
Sep 13 21:09:15 localhost PrimProc[9212]: 15.666481 |0|0|0| C 28 CAL0000: Error decompressing block 1 code=-1 part=8 seg=0

 Comments   
Comment by Ben Thompson (Inactive) [ 2019-09-18 ]

I have not been able to reproduce in my test environment.

Comment by Ben Thompson (Inactive) [ 2019-10-09 ]

Tried again to reproduce and could not. single node install 100g dataset same query as description.
Tested on the released 1.2.5 to DBS and 1.4.0

Comment by Daniel Lee (Inactive) [ 2019-10-11 ]

I tested the issue again on the latest 1.2.5-1 S3 to DBS and did not see this issue again. Please send it back to me and I will close it. Thanks.

Comment by Daniel Lee (Inactive) [ 2019-10-11 ]

No longer reproducible on the final beta release.

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