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

MariaDB asserts in srv_error_monitor_thread at srv0srv.cc:2410

Details

    Description

      The 10.1 branch has been stable for us for a while now.
      10.2 crashes for us on a regular basis, so upgrading is not an option. (See MDEV-16923, and others)

      Unfortunately, 10.1.40 crashed for us with an update on JOINs.
      So we upgraded to 10.1.41, but since we did that the server crashes multiple times a day with the following log message:

      Server version: 10.1.41-MariaDB-1~bionic
      		 
      key_buffer_size=134217728
      		 
      read_buffer_size=131072
      		 
      max_used_connections=192
      		 
      max_threads=502
      		 
      thread_count=45
      		 
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1233831 K  bytes of memory
      		 
      Hope that's ok; if not, decrease some variables in the equation.
      		 
       
      		 
      Thread pointer: 0x7fa04ec10008
      		 
      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 = 0x7f9f52fb3d68 thread_stack 0x49000
      		 
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      		 
      Fatal signal 6 while backtracing

      Attachments

        1. gdb.txt
          208 kB
          Elena Stepanova

        Activity

          People

            marko Marko Mäkelä
            CrewOne Sander Pilon
            Votes:
            0 Vote for this issue
            Watchers:
            7 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.