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

mariadb server crashed on 2 instances at the same time

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.4.13
    • Fix Version/s: 10.4
    • Component/s: Galera
    • Labels:
      None
    • Environment:
      CentOS Linux release 8.1.1911
      MariaDb 10.4.13-MariaDB, for Linux on x86_64
      Galera cluster

      Description

      We have a Galera cluster with 3 nodes on CentOS 8.1, MariaDB 10.4.13, Galera 4

      2 of the 3 nodes crashed at one second interval. Here is the logged information :

      mysqld: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.13/wsrep-lib/src/transaction.cpp:419: int wsrep::transaction::before_commit(): Assertion `state() == s_executing || state() == s_prepared || state() == s_committing || state() == s_must_abort || state() == s_replaying' failed.
      200612 2:24:00 [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 https://mariadb.com/kb/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: 10.4.13-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=7
      max_threads=4002
      thread_count=15
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8938292 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f0cf4000c08
      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 = 0x7f0d07ffdcc8 thread_stack 0x49000

          • buffer overflow detected ***: /usr/sbin/mysqld terminated

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jplindst Jan Lindström
              Reporter:
              mgasco Maurice Gasco
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: