Bug #73914 | mysqladmin does not terminate properly - even when mysqld process is fully gone | ||
---|---|---|---|
Submitted: | 14 Sep 2014 21:02 | Modified: | 15 Sep 2014 8:10 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S2 (Serious) |
Version: | 5.6.20, 5.6.22, 5.7.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | debug builds |
[14 Sep 2014 21:02]
Roel Van de Paar
[14 Sep 2014 21:50]
Roel Van de Paar
Have now confirmed seen this on another statement also (hard to analyze which one as it's a long SQL trace, but clear it's happening), so the issue is not limited to SET GLOBAL INNODB_PURGE_STOP_NOW=ON;
[14 Sep 2014 22:09]
Roel Van de Paar
As a sidenote, a workaround was added to reducer.sh for this as follows; - $MYBASE/bin/mysqladmin -uroot -S$WORKD/socket.sock shutdown >> $WORKD/mysqld.out 2>&1 + # RV-15/9/14 Added timeout due to bug http://bugs.mysql.com/bug.php?id=73914 + timeout -k20 -s9 20s $MYBASE/bin/mysqladmin -uroot -S$WORKD/socket.sock shutdown >> $WORKD/mysqld.out 2>&1
[15 Sep 2014 8:10]
MySQL Verification Team
Hello Roel, Thank you for the bug report and test case. 5.6/5.7 seems to be affected, mysqld-debug process was down but mysqladmin hanged for long( waited 12-15min each time and later Ctr+C manually to end the session). Thanks, Umesh
[15 Sep 2014 8:11]
MySQL Verification Team
Related Bug #73913