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

mysqld crashed few after node is being joined with sst



    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.1, 10.3.4, 10.2
    • 10.1.35, 10.2.17, 10.3.8
    • Galera SST
    • None
    • CentOS 7.4


      mysqld crashed few after node is being joined with sst

      join Node to galera cluster loaded with ~12G data and set wsrep_sst_method=mariabackup

      1. service mysql start --wsrep_cluster_address=gcomm://
        Starting mysql (via systemctl): Job for mariadb.service failed because a timeout was exceeded. See "systemctl status mariadb.service" and "journalctl -xe" for details.

       systemctl status mariadb.service
      ● mariadb.service - MariaDB 10.3.4 database server
         Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
        Drop-In: /etc/systemd/system/mariadb.service.d
         Active: failed (Result: timeout) since Tue 2018-03-20 16:34:15 EET; 1h 7min ago
           Docs: man:mysqld(8)
        Process: 16512 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
        Process: 16509 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
       Main PID: 16601
         CGroup: /system.slice/mariadb.service

       joiner: => Rate:[42.6MiB/s] Avg:[37.3MiB/s] Elapsed:0:03:10
      2018-03-20 16:36:09 0 [Note] WSREP: 1.0 (t4w5): State transfer to 0.0 (t4w3) complete.
      2018-03-20 16:36:09 0 [Note] WSREP: Member 1.0 (t4w5) synced with group.
         joiner: => Rate:[37.8MiB/s] Avg:[37.8MiB/s] Elapsed:0:04:55
      WSREP_SST: [INFO] NOTE: Joiner-Recv-SST took 297 seconds (20180320 16:36:14.043)
      WSREP_SST: [INFO] Preparing the backup at /var/lib/mysql//.sst (20180320 16:36:14.053)
      WSREP_SST: [INFO] Evaluating mariabackup --innobackupex   --apply-log $rebuildcmd ${DATA} &>${DATA}/innobackup.prepare.log (20180320 16:36:14.058            )
      2018-03-20 16:36:16 0 [ERROR] WSREP: Trying to launch slave threads before creating connection at 'gcomm://,,192.16            8.104.195,'
      mysqld: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.4/sql/wsrep_thd.cc:446: void wsrep_create_appliers(lo            ng int): Assertion `0' failed.
      180320 16:36:16 [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.3.4-MariaDB
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467345 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
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.


        Issue Links



              jplindst Jan Lindström (Inactive)
              winstone Zdravelina Sokolovska (Inactive)
              0 Vote for this issue
              6 Start watching this issue



                Git Integration

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