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

Signal 6 after "[Note] WSREP: UP-UP trx conflict for key ..."

    XMLWordPrintable

    Details

      Description

      Two nodes failed with an assertion failure at the same time:

      2022-05-15 20:51:00 9 [Note] WSREP: UP-UP trx conflict for key (2,FLAT8)e6a8a3a7 0237511a: source: 17e55081-d3ba-11ec-ae1f-031dc5dab92f
      version: 5 local: 0 flags: 65 conn_id: 6342 trx_id: 228670428 tstamp: 276357303469703; state:  seqnos (l: 39052478, g: 8142481111, s:
      8142480998, d: 8142480998) WS pa_range: 65535; state history: REPLICATING:0->CERTIFYING:3240 <---> source: bc319d65-d14f-11ec-a78c-a618ebfceb77
      version: 5 local: 1 flags: 65 conn_id: 13905640 trx_id: 1037125527 tstamp: 347389853227489; state:  seqnos (l: 39052389, g: 8142481022, s:
      8142480998, d: 8142480999) WS pa_range: 23; state history: REPLICATING:0->CERTIFYING:3240->APPLYING:1026 Assertion failed: (mode_ == m_local ||
      transaction_.is_streaming()), function <unknown>, file
      /tmp/workspace/Build-Package/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/wsrep-lib/include/wsrep/client_state.hpp, line 668. 220515 20:51: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.6.8-4-MariaDB-enterprise-log
      key_buffer_size=5242880
      read_buffer_size=2097152
      max_used_connections=1501
      max_threads=1502
      thread_count=1600
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18500018 K  bytes of memory
      

      Both nodes did not print any backtrace unless they were submitted with truncation, checking that right now

        Attachments

          Activity

            People

            Assignee:
            hholzgra Hartmut Holzgraefe
            Reporter:
            hholzgra Hartmut Holzgraefe
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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