[MDEV-10937] MariaDB crash when executing DDL scripts in bulk Created: 2016-10-02  Updated: 2016-11-04  Resolved: 2016-11-04

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table
Affects Version/s: 10.1.10
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: ManasaTulluri Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: need_feedback
Environment:

Linux 2.6.32-642.el6.x86_64 total memory in server - 7.5 GB

Attachments: File WKF_INST_HIST.sql     PNG File error_crash.png     PNG File mariadb_error_log.png    

 Description   

Hi ,

I am running one control/master script which in turn calls 150 DDL scripts. Mariadb server crashed in between. There is no error when the scripts are run individually. This is a serious issue and has caused downtime for us.

error_crash.png :- Has exact error while running the script WKF_INST_HIST.sql
mariadb_error_log.png :- screenshot from /mariadb/bin/logs/db_logs/error_mariadb.log (tail -100),
Could not find relevant error in the logfile.
WKF_INST_HIST.sql :- SQL script during which execution resulted in crash. Script works fine when it was run individually.

Thanks & Regards,
Manasa Tulluri.

 Comments   
Comment by Elena Stepanova [ 2016-10-02 ]

Manasa,
Please check your system logs for messages from OOM killer at the time when you lost connection to the server.
If the problem is repeatable, next time when you run the scripts please set up a periodic memory monitor (e.g. top in batch mode, or any tool of your choice as long as it shows memory consumption for mysqld process as well as for the whole system). After the MariaDB server disappears, please collect the output of the monitor and attach it as well.
Please also attach or paste your cnf files.
Thanks.

Comment by ManasaTulluri [ 2016-10-06 ]

Hi Elena,

Yes, this is because of OOM killer, we have verified /var/log/messages. We are also closely following up with Valerii Kravchuk <issue-12469@support.mariadb.com> using support case.

Thank you.

Comment by Valerii Kravchuk [ 2016-11-04 ]

According to further investigation results OOM killer had to kill mysqld because of misconfiguration (allocating too much memory for some global buffers for the load and memory avaiable). This was not a result of any bug in the code.

I am closing this as "Not a bug". Please, report a new bug in case of similar problem that is not caused by misconfiguration.

Generated at Thu Feb 08 07:46:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.