[MDEV-13373] Shutdown never completes : Waiting for master thread to exit Created: 2017-07-22 Updated: 2017-09-04 Resolved: 2017-09-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.1.24 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Tom | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
Fedora 25 64bit |
||
| Attachments: |
|
| Description |
|
When MariaDB is shutdown (via systemd), it never finishes. The mysqld process jumps to 100% CPU, and the log file repeats
at regular intervals. Killing (with kill -KILL) the mysqld process is the only way to proceed. I've left it for hours with no change.
|
| Comments |
| Comment by Tom [ 2017-07-22 ] |
|
Also occurs on FC24 |
| Comment by Alice Sherepa [ 2017-07-25 ] |
|
please provide your .cnf file(s), error.log and collect gdb stack traces |
| Comment by Tom [ 2017-07-25 ] |
|
Cnf's attached, along with fuller log entries strace -p 18308 (gdb) bt |
| Comment by Tom [ 2017-08-01 ] |
|
This has fixed itself as of # rpm -qi mariadb-server |
| Comment by Elena Stepanova [ 2017-08-04 ] |
|
Tom, Would you be able to setup the server to produce a coredump and next time when it hangs, kill it with SIGABRT rather than SIGKILL? Further, would you be willing to substitute mysqld with a debug binary for one cycle and get a debug stack trace and the coredump with it? |
| Comment by Tom [ 2017-08-07 ] |
|
Well, it doesn't reproduce in later versions of MariaDB Fedora ship (though it was consistently broken), so I think we can just close this. |
| Comment by Elena Stepanova [ 2017-09-04 ] |
|
According to the comment above, closing for now; but please comment if the problem re-appears. |