[MDEV-18051] Connect engine crashes mariadb server Created: 2018-12-21  Updated: 2022-07-11  Resolved: 2018-12-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.2.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Pierre Assignee: Olivier Bertrand
Resolution: Cannot Reproduce Votes: 0
Labels: connect-engine, flush
Environment:

Windows Server 2016 Standard 64bit
Processor: Intel(R) Xeon(R) CPU E5640 @2.67GHz 2.66GHz
RAM: 24GB


Attachments: File flush.err     File my.ini    
Issue Links:
Relates
relates to MDEV-29079 Server crashes in CntCloseTable/ha_co... Open

 Description   

When I run flush tables the server crashes. We use the connect engine quite intensively and the mysqld memory keeps growing, so I run flush tables to free up some memory, but the DB server crashes.

I will attach the error log for that query.



 Comments   
Comment by Elena Stepanova [ 2018-12-21 ]

Stack trace from the attached log:

10.2.8

ha_connect.dll!CntCloseTable()[connect.cc:546]
ha_connect.dll!ha_connect::CloseTable()[ha_connect.cc:2014]
mysqld.exe!closefrm()[table.cc:3412]
mysqld.exe!intern_close_table()[table_cache.cc:223]
mysqld.exe!tc_purge()[table_cache.cc:335]
mysqld.exe!close_cached_tables()[sql_base.cc:376]
mysqld.exe!reload_acl_and_cache()[sql_reload.cc:331]
mysqld.exe!mysql_execute_command()[sql_parse.cc:5387]
mysqld.exe!mysql_parse()[sql_parse.cc:7891]
mysqld.exe!dispatch_command()[sql_parse.cc:1814]
mysqld.exe!do_command()[sql_parse.cc:1359]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:346]
mysqld.exe!tp_callback()[threadpool_common.cc:192]
ntdll.dll!RtlReleaseSRWLockExclusive()
ntdll.dll!RtlReleaseSRWLockExclusive()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2c0b3bcbbc0): flush tABLES
Connection ID (thread ID): 24138
Status: NOT_KILLED

Comment by Olivier Bertrand [ 2018-12-24 ]

I cannot reproduce this. When I execute FLUSH TABLES the connect engine is not called. Could you publish the scenario causing the crash?

And what is this mysqld memory that keeps growing? Is it related to CONNECT?

Comment by Pierre [ 2018-12-30 ]

I was also not able to reproduce this. You can close the issue. I will reopen when I found the table causing the issue

Generated at Thu Feb 08 08:41:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.