Bug #95547 MySQL restarts automatically after ABORT_SERVER due to disk full
| Submitted: | 27 May 2019 14:37 | Modified: | 31 May 2019 11:53 |
|---|---|---|---|
| Reporter: | Przemyslaw Malkowski | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.7.26 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[27 May 2019 14:37]
Przemyslaw Malkowski
[31 May 2019 11:53]
MySQL Verification Team
Hello Przemyslaw, Thank you for the report. Since default value (>= 5.7.7) of binlog_error_action is ABORT_SERVER, which makes the server halt logging and shut down whenever it encounters such an error with the binary log. But with mysqld_safe(I assume this in your case) or any other homegrown monitoring process which attempt to restart mysqld, as you rightly pointed out "MySQL service is auto-restarted, which can cause problems and maybe even data damage as recovery cannot finish properly if the disk is still full", or scenarios like our Shane's Bug #88299 etc. regards, Umesh
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.