[MCOL-380] test007 regression test fails - amazon EC2 centos-7 Created: 2016-10-28  Updated: 2017-06-05  Resolved: 2017-06-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: 1.0.4
Fix Version/s: 1.0.9

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

amazon EC2 single server centos7 os system, c4.2xlarge



 Description   

regression testing on amazon system reported errors, where the test passes on my virtualbox centos7 VM. test007 is failing in this case

Oct 28 15:58:03 ip-172-30-0-125 PrimProc[558]: 03.520452 |0|0|0| C 28 CAL0000: Snapshot too old
Oct 28 15:58:03 ip-172-30-0-125 PrimProc[558]: 03.520581 |0|0|0| C 28 CAL0000: Snapshot too old
Oct 28 15:58:03 ip-172-30-0-125 joblist[691]: 03.521721 |3496|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.

Oct 28 15:58:03 ip-172-30-0-125 Calpont[691]: 03.521557 |0|0|0| E 00 CAL0000: /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/dbcon/joblist/batchprimitiveprocessor-jl.cpp@660: assertion 'in.length() > offset' failed
Oct 28 15:58:03 ip-172-30-0-125 joblist[691]: 03.521721 |3496|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.

------------------------------------------------------------------------------------

some input from D Hall

The VSS versions every time there's a DLL statement. It can only hold so many versions, and then starts dropping old ones. When a query begins, it gets the current version. If, during it's processing, so many DLL statements come in that it's version is aged out, then you get this message.



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

hill I'm assuming this is no longer an issue, if so can you close?

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