[MDEV-8447] alter table loops internally and fills up disk Created: 2015-07-10  Updated: 2015-07-21  Resolved: 2015-07-21

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table
Affects Version/s: 10.0.16
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Frank Schröder Assignee: Jan Lindström (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Environment:

10.0.16-MariaDB-log openSUSE package
SLES 12

Attachments: Zip Archive dummy.zip    
Issue Links:
Relates
relates to MDEV-8386 MARIADB creates very big tmp file > 3... Closed

 Description   

In a fresh MariaDB when I import a small 9MB InnoDB Table and enter OPTIMIZE LOCAL TABLE the server hangs/loops and fills the disk 100% with one huge #sql...ibd file. The mysqld has then to be stopped with kill -9...
As written in the documentation the server performs an ALTER TABLE engine=InnoDB, so there is the same effect when I enter the ALTER directly, also on ALTER TABLE ADD KEY and so on. No difference if there are already keys on the table or not. If the table contains less than ~10000 rows, it works fine.
Workarounds:
1) change the engine to MyIsam and then back to InnoDB
2) set old_alter_table=ON (preferred)

 Comments   
Comment by Elena Stepanova [ 2015-07-12 ]

oldschool,

What exactly do you mean by importing the table? (There are several actions that can be called this way, so specifics is important).
Can you provide the table that you are importing, in whatever form you have it?
You set 'affects version' to Galera, is it what you are really using?
Please also provide your cnf file(s).
Thanks.

Comment by Elena Stepanova [ 2015-07-13 ]

Thank you.
Once again, I can reproduce it on openSUSE (on their binaries), but not on another system, so it must be closely related to, or a duplicate of, MDEV-8386.

Comment by Jan Lindström (Inactive) [ 2015-07-21 ]

Closing as duplicate.

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