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

LP #1673049: Crash caused by a delete from a table without a primary key


    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None


      **Reported in Launchpad by Ceri WIlliams last update 15-03-2017 11:55:32

      Percona Server 5.6.19-67.0-log

      A delete from a table on the master appears to have triggered every slave to crash. The table that appears to be the cause should only have 1 or 2 rows and so does not have an explicit primary key defined. The table showed a difference as a result of a checksum and a delete was issued: delete from x limit 2

      The stracktrace that appeared was:

      08:27:24 UTC - mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
      Please help us make Percona Server better by reporting any
      bugs at http://bugs.percona.com/

      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1229753 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7ef64c000990
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 7efea076d890 thread_stack 0x40000

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0): is an invalid pointer
      Connection ID (thread ID): 2
      Status: NOT_KILLED

      This appears to support the delete causing the issue, further supported by rebuilding a slave from a PXB backup and replicating until the point of the delete, changing replication postition to the next event and resuming replication (no issue seen)

        Smart Checklist


            Issue Links



                • Assignee:
                  lpjirasync lpjirasync (Inactive)
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: