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

Deadlock found when trying to get lock; try restarting transaction, Error_code: 1213

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.16
    • 10.6
    • Galera
    • None

    Description

      Our architecture is 3-node galera cluster - 2 DB nodes + 1 arbitrator in different locations. Plus running haproxy as the front end.

      One of the DB nodes (node 2) hit a series of error, with the first one as follows:
      2025-01-05 0:51:33 108 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table bes_core.tb_message_queue_medium_logger; Deadlock found when trying to get lock; try restarting transaction, Error_code: 1213; handler error HA_ERR_LOCK_DEADLOCK; the event's master log FIRST, end_log_pos 217, Internal MariaDB error code: 1213

      This node was removed from the cluster. When we tried to restart it, it required SST to re-form the cluster.

      I will upload the maria-error.log for node 1 and 2 for your review.

      Attachments

        1. mariadb-error.log-node1
          2.00 MB
          Lawrence Man
        2. mariadb-error.log-node2
          88 kB
          Lawrence Man

        Activity

          There are no comments yet on this issue.

          People

            janlindstrom Jan Lindström
            LawrenceMan Lawrence Man
            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.