Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.24
-
None
-
3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Description
Scenario:
Bash console (it's mandatory to execute from the bash):
1) mysql -h 127.0.0.1 --port=3306 -u user -ppassword db -e 'DROP TABLE IF EXISTS c1;'
2) mysql -h 127.0.0.1 --port=3306 -u user -ppassword db -e 'CREATE TABLE c1 ENGINE=CONNECT TABLE_TYPE=MYSQL DBNAME='\''information_schema'\'' OPTION_LIST='\''host=127.0.0.1,port=33235,user=user,password=password'\'' `tabname`='\''tables'\'''
3) mysql -h 127.0.0.1 --port=3306 -u user -ppassword db -e 'CREATE TABLE t1 AS SELECT * FROM c1'
This scenario leads to spending an additional 500 MB (equal to value of "connect_work_size" variable) of virtual memory for each repetition. This memory is not released until you restart the mysql process. Remote database name and a table - can be any.
Attachments
Issue Links
- is part of
-
MDEV-10496 Connect Engine: CREATE TABLE memory leak
-
- Closed
-
Sergey.Antonyuk,
You've said "for each repetition". Do you mean that on the same running server you get the memory keep growing indefinitely by just repeating DROP/CREATE/CREATE as above? Can you show it – results of some memory monitor, e.g. top (or whatever you use)?
I can of course observe the 500MB growth with the corresponding connect_work_size, but it's a one-time event for me.