Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-4759

Percona Server Crashing when the stored procedure called the second time in the same session

Details

    • Bug
    • Status: Done
    • Medium
    • Resolution: Fixed
    • 5.7.21-21, 5.7.22-22
    • 5.7.26-29
    • None
    • Percona Server 5.7.21 & 5.7.22 

    Description

      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.

      1. create schema (few tables)
      2. create views
      3. insert sample test data
      4. 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.

      Attachments

        Issue Links

          Activity

            People

              amonar Anton Matvienko
              uday.varagani Uday Varagani (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 53 minutes Original Estimate - 53 minutes
                  53m
                  Remaining:
                  Time Spent - 1 hour, 8 minutes Remaining Estimate - 53 minutes
                  53m
                  Logged:
                  Time Spent - 1 hour, 8 minutes Remaining Estimate - 53 minutes
                  1h 8m

                  Smart Checklist