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

Galera InnoDB: BF-BF X lock conflict,mode

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      MariaDB 10.5.6
      Galera (3 NODES)
      We received the following message on one of the nodes:

      2021-11-02 13:24:40 6 [Note] InnoDB: BF-BF X lock conflict,mode: 1027 supremum: 0conflicts states: my executing locked executing
      RECORD LOCKS space id 630 page no 4 n bits 328 index GEN_CLUST_INDEX of table `amulex`.`myphp_cache` trx id 355629422 lock_mode X locks rec but not gap
      Record lock, heap no 2 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6da; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc30110; asc        ;;
       3: len 23; hex 69645f325f6f72646572735f6c6973745f736561726368; asc id_2_orders_list_search;;
       4: len 6; hex 373934353037; asc 794507;;
       
      Record lock, heap no 3 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6db; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc3011f; asc        ;;
       3: len 18; hex 69645f325f6f72646572735f66696c746572; asc id_2_orders_filter;;
       4: len 3; hex 706179; asc pay;;
                    
      Record lock, heap no 4 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6dc; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc3012e; asc       .;;
       3: len 23; hex 69645f325f6f72646572735f766965775f736561726368; asc id_2_orders_view_search;;
       4: len 0; hex ; asc ;;
       
      Record lock, heap no 5 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6dd; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc3013d; asc       =;;
       3: len 30; hex 69645f325f6f72646572732d636f6e74616374735f313335385f6c697374; asc id_2_orders-contacts_1358_list; (total 37 bytes);
       4: len 0; hex ; asc ;;
       
      Record lock, heap no 6 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6de; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc3014c; asc       L;;
       3: len 30; hex 69645f325f6f72646572732d6576656e74735f313335385f6c6973745f73; asc id_2_orders-events_1358_list_s; (total 35 bytes);
       4: len 0; hex ; asc ;;
       
      Record lock, heap no 7 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
       0: len 6; hex 000000a7c6df; asc       ;;
       1: len 6; hex 000006713ba7; asc    q; ;;
       2: len 7; hex 9300000dc3015b; asc       [;;
       3: len 30; hex 69645f325f6f72646572732d636f6e74616374735f313336325f6c697374; asc id_2_orders-contacts_1362_list; (total 37 bytes);
       4: len 0; hex ; asc ;;
      

      and messages like "Record lock," kept appearing
      command
      kill $id
      did not give a result

      Restarting the NODE did not give a result, because after the launch, the same messages appeared in the logs again, while the node itself did not enter the Cluster

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivyrva@amulex.ru Vyrva Igor
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.