[MDEV-14714] mysqld writes status information on HUP signal into innodb data file, breaking it Created: 2017-12-19  Updated: 2018-01-08  Resolved: 2017-12-20

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.2.11
Fix Version/s: 10.2.12

Type: Bug Priority: Major
Reporter: Alexander Mikhailov Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

FreeBSD 11.1-RELEASE-p4 amd64
build from port databases/mariadb102-server


Issue Links:
Duplicate
duplicates MDEV-14889 Server fails to start because of aria... Closed
is duplicated by MDEV-14337 mysqld_safe may suppress error messag... Closed
is duplicated by MDEV-14644 MariaDB 10.2.11 breaks binary logging... Closed
Relates
relates to MDEV-14488 logging not happening on spider branc... Closed

 Description   

Steps to reproduce on FreeBSD 11.1 amd64 box

cd /usr/ports/databases/maraidb102-server
 
make install
 
select only INNODB engine and GSSAPI_NONE
 
service mysql-server onestart
 
killall -HUP mysqld
 
head /var/db/mysql/ibdata1

You will see a "Status information" here, instead of error_log file. It breaks database completely, mysqld will hung or crash in seconds depending on load

On production server also error_log file will be flooded with gigs of binary data which I think are actual data should be written into ibdata1

10.2.10 is not affected, 10.2.11 on Ubuntu 16.04 from official repo also isn't affected

 Comments   
Comment by Sergei Golubchik [ 2017-12-20 ]

This is most probably the same bug as MDEV-14488, which was fixed in MDEV-14337. And will be released in 10.2.12

Comment by Alexander Mikhailov [ 2017-12-20 ]

Sergei, could you please give me a link to github commit for this patch?
I can't find anything for MDEV-14337

Comment by Alexander Mikhailov [ 2017-12-20 ]

Sorry, I found it https://github.com/mariadb/server/commit/36f84744031430747d27bfb2087c7ae51019a70a

I confirm, it solves the problem.

Comment by Sergei Golubchik [ 2017-12-20 ]

Thanks, closing.

Comment by Jonathan Nicol [ 2018-01-03 ]

your current GA version has a huge bug that can easily cause data corruption... don't you think you should pull this version from the download page??

Comment by Hartmut Holzgraefe [ 2018-01-05 ]

The problem unfortunately seems to have existed since MariaDB 10.2.4 already, so just pulling the latest version wouldn't have solved that much ...

Generated at Thu Feb 08 08:15:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.