Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6011

mariaDB slave crash

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • None
    • None
    • None
    • None
    • Server version: 5.5.31-MariaDB-log MariaDB Server system: centos 6.3

    Description

      MariaDB 5.5 bug?

      MySQL thread id 10080998, OS thread handle 0x7f020c9f4700, query id 725990157 10.200.100.22 tmsq Sending data
       
      SELECT job.* FROM 
       
      (
       
       
       
      SELECT
       
        tmsorder1_.tms_order_id
       
      FROM 
       
        TMS_ORDER tmsorder1_ 
       
        STRAIGHT_JOIN   TMS_ORDER_OTHER_INFO tmsorderot2_ ON tmsorder1_.tms_order_id= tmsorderot2_.tms_order_id
       
      WHERE  (tmsorder1_.ORDER_STATUS IN(3,4,5,7,-2))
       
          AND (tmsorder1_.MERGE_FLAG IN(0, 1))
       
          AND tmsorder1_.JOIN_TIME >= TIMESTAMPADD(DAY, - 93, NOW())
       
             
       
          AND (tmsorderot2_.AUTO_FREIGHT IS NULL
       
                OR tmsorderot2_.AUTO_FREIGHT = 0)
       
      ) t 
       
      inner join  tms_job job 
       
      ON job.tms_order_id = t.tms_order_id
       
      WHERE (job.JOB_TYPE IN(2, 5))
       
          AND (job.IS_COUNT_FEE IS NULL
       
                OR job.IS_COUNT_FEE = 1) limit 2000

      140329 11:42:17  InnoDB: Assertion failure in thread 139646778427136 in file btr0pcur.c line 254
       
      InnoDB: We intentionally generate a memory trap.
       
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
       
      InnoDB: If you get repeated assertion failures or crashes, even
       
      InnoDB: immediately after the mysqld startup, there may be
       
      InnoDB: corruption in the InnoDB tablespace. Please refer to
       
      InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
       
      InnoDB: about forcing recovery.
       
      140329 11:42:17 [ERROR] 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.
       
       
       
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
       
       
       
      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.
       
       
       
      Server version: 5.5.31-MariaDB-log
       
      key_buffer_size=2147483648
       
      read_buffer_size=4194304
       
      max_used_connections=143
       
      max_threads=3002
       
      thread_count=39
       
      It is possible that mysqld could use up to 
       
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 39039253 K  bytes of memory
       
      Hope that's ok; if not, decrease some variables in the equation.

      Attachments

        Activity

          People

            elenst Elena Stepanova
            wshxgxiaoli xiaogang huang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.