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

SQL slave crash loop issue

    XMLWordPrintable

Details

    Description

      We have seen this a few times in the last few months but never managed to find a cause.
      The server seems to be running fine, maybe a little slow. but the service keeps crashing the slaving never catches up.

      [root@sql01]# systemctl status mariadb
      ● mariadb.service - MariaDB 10.4.21 database server
      Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
      └─mariadb-jemalloc.conf, migrated-from-my.cnf-settings.conf
      Active: active (running) since Wed 2022-06-08 06:49:18 UTC; 25s ago
      Docs: man:mysqld(8)
      https://mariadb.com/kb/en/library/systemd/
      Process: 189081 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
      Process: 188745 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
      Process: 188741 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
      Main PID: 188986 (mysqld)
      Status: "To roll back: 1 transactions, 1915813 rows"
      CGroup: /system.slice/mariadb.service
      └─188986 /usr/sbin/mysqld

      2022-06-08 6:51:02 12 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table ; Lock wait timeout exceeded; try restarting transaction, Error_code: 1205; handler error HA_ERR_LOCK_WAIT_TIMEOUT; the event's master log mysql-bin.000899, end_log_pos 854181414, Gtid 0-2-168024604, Internal MariaDB error code: 1205
      2022-06-08 6:51:04 0 [Note] InnoDB: To roll back: 1 transactions, 819812 rows
      2022-06-08 6:51:19 0 [Note] InnoDB: To roll back: 1 transactions, 552868 rows
      2022-06-08 6:51:34 0 [Note] InnoDB: To roll back: 1 transactions, 211694 rows
      2022-06-08 6:51:43 0 [Note] InnoDB: Rolled back recovered transaction 1230118347
      2022-06-08 6:51:43 0 [Note] InnoDB: Rollback of non-prepared transactions completed
      2022-06-08 6:56:02 0 [Note] InnoDB: Using Linux native AIO
      2022-06-08 6:56:02 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-06-08 6:56:02 0 [Note] InnoDB: Uses event mutexes
      2022-06-08 6:56:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2022-06-08 6:56:02 0 [Note] InnoDB: Number of pools: 1
      2022-06-08 6:56:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-06-08 6:56:02 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 4, chunk size = 128M
      2022-06-08 6:56:02 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-06-08 6:56:02 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-06-08 6:56:02 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1566056169553

      Attachments

        Activity

          People

            Unassigned Unassigned
            maria.joseph@telrock.com maria joseph
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.