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

Mariadb 10.5.10 crash during IST



    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.5.10
    • Fix Version/s: None
    • Component/s: Galera
    • Labels:
    • Environment:
      CentOS Linux release 8.2.2004 (Core)


      The MariaDB server has crashed after trying to sync with the primary-active node during IST. I've uploaded 6 CSV files on the primary node with 2,3MBytes in size and after that inactive node Test5 has crashed after trying to synchronize during IST.
      After loading/insert of thrird CSV file Gcacge has been created "Created page /var/lib/mysql/gcache.page.000000 of size 134217728 bytes".
      CSV file is 2.3 MBytes and after the third, it is creating a new cache page with 128MB.
      Gcache settings: gcache.page_size = 128M; gcache.size = 4G;

      Test4 server was active, test5 was trying to sync data and it crashes after 51.4% with the message

      terminate called after throwing an instance of 'std::bad_alloc'
      what(): std::bad_alloc
      210616 10:54:31 [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.5.10-MariaDB-log
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467871 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x49000
      Can't start addr2line
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Fatal signal 11 while backtracking

      Also, primary node Test4 goes into non-primary from Primary

      wsrep_local_state_comment Initialized
      wsrep_cluster_status non-Primary


        1. test4.cnf.txt
          3 kB
        2. test4.log.txt
          39 kB
        3. test5.cnf.txt
          3 kB
        4. test5.log
          82 kB



            Unassigned Unassigned
            shexphobos Xesh
            1 Vote for this issue
            3 Start watching this issue



                Git Integration