[MCOL-33] 200: Monitor UM Memory Failed Created: 2016-05-03  Updated: 2016-05-23  Resolved: 2016-05-23

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

Type: Task Priority: Major
Reporter: Dipti Joshi (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None

Sprint: MCOL Sprint 2 - Priority 2

 Description   

200 Monitor TotalUmMemory: Failed (check test200/diff.txt)

TEST200 : df -h output:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 185G 90G 86G 52% /
tmpfs 3.9G 15M 3.9G 1% /dev/shm



 Comments   
Comment by David Hill (Inactive) [ 2016-05-20 ]

different errors in memory settings and mysql server crash

root@srvss2 srvswdev11]# more test200/diff.txt
3,4c3
< count2
< 130000000

> ERROR 1815 (HY000) at line 6: Internal error: InetStreamSocket::readToMagic: Remote is closed
6,49c5,31
< 0
< ERROR 122 (HY000) at line 10: IDB-2003: Aggregation/Distinct memory limit is exceeded.
< sleep(30)
< 0
< count4
< 100761020
< count5
< 100761020
< sleep(30)
< 0
< ERROR 122 (HY000) at line 19: IDB-2001: Join or subselect exceeds memory limit.
< sleep(30)
< 0
< count7
< 88907548
< count8
< 88907548
< sleep(30)
< 0
< ERROR 122 (HY000) at line 28: IDB-2001: Join or subselect exceeds memory limit.
< sleep(30)
< 0
< count10
< 136000000
< count11
< 136000000
< sleep(30)
< 0
< ERROR 122 (HY000) at line 37: IDB-2002: Union memory limit exceeded.
< sleep(60)
< 0
< count13
< 68000000
< F count14
< 1 68000000
< sleep(30)
< 0
< ERROR 122 (HY000) at line 47: IDB-2003: Aggregation/Distinct memory limit is exceeded.
< sleep(30)
< 0
< ERROR 122 (HY000) at line 55: CAL0002: Update Failed: IDB-2001: Join or subselect exceeds memory limit.
< count16
< 51372630
< ERROR 122 (HY000) at line 61: IDB-2001: Join or subselect exceeds memory limit.

> 1
> ERROR 2006 (HY000) at line 10: MySQL server has gone away
> ERROR 2006 (HY000) at line 11: MySQL server has gone away
> ERROR 2006 (HY000) at line 14: MySQL server has gone away
> ERROR 2006 (HY000) at line 15: MySQL server has gone away
> ERROR 2006 (HY000) at line 16: MySQL server has gone away
> ERROR 2006 (HY000) at line 19: MySQL server has gone away
> ERROR 2006 (HY000) at line 20: MySQL server has gone away
> ERROR 2006 (HY000) at line 23: MySQL server has gone away
> ERROR 2006 (HY000) at line 24: MySQL server has gone away
> ERROR 2006 (HY000) at line 25: MySQL server has gone away
> ERROR 2006 (HY000) at line 28: MySQL server has gone away
> ERROR 2006 (HY000) at line 29: MySQL server has gone away
> ERROR 2006 (HY000) at line 32: MySQL server has gone away
> ERROR 2006 (HY000) at line 33: MySQL server has gone away
> ERROR 2006 (HY000) at line 34: MySQL server has gone away
> ERROR 2006 (HY000) at line 37: MySQL server has gone away
> ERROR 2006 (HY000) at line 38: MySQL server has gone away
> ERROR 2006 (HY000) at line 42: MySQL server has gone away
> ERROR 2006 (HY000) at line 43: MySQL server has gone away
> ERROR 2006 (HY000) at line 44: MySQL server has gone away
> ERROR 2006 (HY000) at line 47: MySQL server has gone away
> ERROR 2006 (HY000) at line 48: MySQL server has gone away
> ERROR 2006 (HY000) at line 52: MySQL server has gone away
> ERROR 2006 (HY000) at line 55: MySQL server has gone away
> ERROR 2006 (HY000) at line 58: MySQL server has gone away
> ERROR 2006 (HY000) at line 61: MySQL server has gone away

Comment by Dipti Joshi (Inactive) [ 2016-05-22 ]

Latest nightly run log has now improved - though not completely clear

hill Here is the analysis of this log: cat test200/diff.txt
7c7
< ERROR 122 (HY000) at line 10: IDB-2003: Aggregation/Distinct memory limit is exceeded.

> ERROR 1815 (HY000) at line 10: Internal error: IDB-2003: Aggregation/Distinct memory limit is exceeded.
16c16
< ERROR 122 (HY000) at line 19: IDB-2001: Join or subselect exceeds memory limit.

> ERROR 1815 (HY000) at line 19: Internal error: IDB-2001: Join or subselect exceeds memory limit.
20c20
< 88907548

> 18907548
22c22
< 88907548

> 18907548
25c25,26
< ERROR 122 (HY000) at line 28: IDB-2001: Join or subselect exceeds memory limit.

> count9
> 18907551
34c35
< ERROR 122 (HY000) at line 37: IDB-2002: Union memory limit exceeded.

> ERROR 1815 (HY000) at line 37: Internal error: IDB-2002: Union memory limit exceeded.
43c44
< ERROR 122 (HY000) at line 47: IDB-2003: Aggregation/Distinct memory limit is exceeded.

> ERROR 1815 (HY000) at line 47: Internal error: IDB-2003: Aggregation/Distinct memory limit is exceeded.
46c47
< ERROR 122 (HY000) at line 55: CAL0002: Update Failed: IDB-2001: Join or subselect exceeds memory limit.

> ERROR 1815 (HY000) at line 55: Internal error: CAL0002: Update Failed: IDB-2001: Join or subselect exceeds memory limit.
49c50
< ERROR 122 (HY000) at line 61: IDB-2001: Join or subselect exceeds memory limit.

> ERROR 1815 (HY000) at line 61: Internal error: IDB-2001: Join or subselect exceeds memory limit.

Where ever the mis-match is due to ERROR 122 vs ERROR 1815 - is not true failure - It is due the fact that MariaDB ColumnStore that is based on MariaDB Server uses error number 1815, where as the reference log is showing old error number of 122 - Other wise the text of the error is essentially the same.

Hence test200/memLimits.sql.ref.log needs to be updated as following
(1) replace line 7 with "ERROR 1815 (HY000) at line 10: Internal error: IDB-2003: Aggregation/Distinct memory limit is exceeded."
(2) replace line 16 with "ERROR 1815 (HY000) at line 19: Internal error: IDB-2001: Join or subselect exceeds memory limit."
(3) replace line 35 with "ERROR 1815 (HY000) at line 37: Internal error: IDB-2002: Union memory limit exceeded."
(4) replace line 43 with "ERROR 1815 (HY000) at line 47: Internal error: IDB-2003: Aggregation/Distinct memory limit is exceeded."
(5) replace line 46 with "ERROR 1815 (HY000) at line 55: Internal error: CAL0002: Update Failed: IDB-2001: Join or subselect exceeds memory limit."
(6) replace line 49 with "ERROR 1815 (HY000) at line 61: Internal error: IDB-2001: Join or subselect exceeds memory limit."

Above changes will clear out these differences - however mismatch at line 20, 22 and 25 will still remain.
hill After you make this update, on Monday morning let us manually run this test to gather, I will be able to help figure out the mismatch in 20,22 and 25 as well when we do that - as I need to see the actual data in the test table test200 to diagnose it.

Comment by David Hill (Inactive) [ 2016-05-22 ]

made the changes to the ref logs

Comment by Dipti Joshi (Inactive) [ 2016-05-23 ]

Not failing any more - so closing

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