Percona Server Crashing when the stored procedure called the second time in the same session
General
Escalation
General
Escalation
Description
Environment
Percona Server 5.7.21 & 5.7.22
AFFECTED CS IDs
232030
Attachments
1
- 11 Apr 2022, 11:32 AM
Smart Checklist
Activity
Show:
Kamil Holubicki October 25, 2022 at 1:06 PM
Done
Details
Details
Assignee
Anton Matvienko
Anton MatvienkoReporter
Uday Varagani
Uday Varagani(Deactivated)Labels
Upstream Bug URL
Needs Review
Yes
Original estimate
Time tracking
Fix versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created August 22, 2018 at 1:28 PM
Updated March 6, 2024 at 12:55 PM
Resolved April 26, 2022 at 10:10 AM
Hi Team,
Customer has PXC set up where second INSERT into a table is crashing the server. It is told that there is an INSERT AFTER trigger for this table where a stored procedure is being called. Later, we could see even calling the stored procedure second time in the same session is resulting the crash.
How to repeat.
A SQL script having the queries required to re produce this are attached. I can say there are below steps.
create schema (few tables)
create views
insert sample test data
create stored procedure.
Now, you can re produce the crash either by doing the INSERTs as below
mysql> INSERT INTO `test` VALUES (4,'new domain sample1/test',12345,1,'0x0003','Y',0,'2018-07-04 10:53:58'); Query OK, 1 row affected (0.20 sec) mysql> INSERT INTO `test` VALUES (5,'new domain samepl2/test',12345,1,'0x0004','Y',0,'2018-07-04 10:53:58'); ERROR 2013 (HY000): Lost connection to MySQL server during query
OR by calling the stored procedure twice as given below.
mysql> CALL method_duplicate_checker ("new domain sample1/test", "0x0001", @ret) ; Query OK, 0 rows affected (0.10 sec) mysql> CALL method_duplicate_checker ("new domain sample2/test", "0x0001", @ret) ; ERROR 2013 (HY000): Lost connection to MySQL server during query
Please look into this.