Bug #36317 Running tests from large_tests suite hangs mysqld

• Submitted: 24 Apr 2008 14:00
• Modified: 28 Aug 2008 16:24
• Reporter: Hakan Küçükyılmaz
• Status: Closed
• Category: Tests: Engine
• Severity: S3 (Non-critical)
• Version: 6.0, 6.0-falcon tree
• OS: Linux
• CPU Architecture: Any

[24 Apr 2008 14:00] Hakan Küçükyılmaz

Description:
Running Falcon tests from large_tests suite hangs mysqld.

How to repeat:
./mysql-test-run.pl --skip-ndb --enable-disabled --force --big-test --suite-timeout=6360 --testcase-timeout=795 --suite=large_tests

alter_table.test hangs.

[15:58] root@test>show processlist;
+----+------+-----------------+------+---------+------+--------------+---------------------------------+
| Id | User | Host            | db   | Command | Time | State        | Info                            |
+----+------+-----------------+------+---------+------+--------------+---------------------------------+
|  1 | root | localhost       | test | Query   | 3039 | Sending data | insert into t1 select * from t1 |
|  4 | root | localhost:47301 | test | Query   |    0 | NULL         | show processlist                |
+----+------+-----------------+------+---------+------+--------------+---------------------------------+
2 rows in set (0.00 sec)

Suggested fix:
Don't hang

[24 Apr 2008 14:01] Hakan Küçükyılmaz

Backtrace of all threads while mysqld is hanging

Attachment: thread_status_36317.txt (text/plain), 11.90 KiB.

[25 Apr 2008 5:27] Sveta Smirnova

Thank you for the report.

Hang verified as described.

[30 Apr 2008 18:43] Philip Stoev

It appears that the machine went out of this space and MyISAM started to sleep() until disk space becomes available.

[28 Aug 2008 7:56] Sveta Smirnova

Hakan,

currently test alter_table fails with "mysqltest: At line 32: query 'insert into t1 select * from t1' failed: 20: Disk is full writing './test/t1.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs" Can it be considered as correct behavior?

[28 Aug 2008 8:50] Hakan Küçükyılmaz

Sveta,

yes, that error message is very good and the end user clearly sees why everything stopped.

Best regards,

Hakan

[28 Aug 2008 16:24] Paul DuBois

There's no bug here, so no changelog entry needed.