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

[ERROR] WSREP: FSM: no such a transition APPLYING -> COMMITTED



    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.10, 10.6.14
    • None
    • Galera, Server
    • None
    • redhat 7 on VMware


      One of our DB is using 2 DB nodes + 1 aribtrator architecture with HAProxy on top. Original version is DB nodes MariaDB 10.6.10 and Galera 26.4.12.

      We upgraded one DB node to MariaDB 10.6.14 (Galera 26.4.14) and switched HAPRoxy new traffic to this upgraded DB node. At this point, one DB node is 10.6.14 (Galera 26.4.14) and another DB node is 10.6.10 (Galera 26.4.12). Both nodes have connections from app. After 3 minutes, encountered FSM error in 10.6.14 node. The crashed node restarted automationally and can join back cluster. However, ~3 mins later, it will crash again. This behavior kept repeating.

      [ERROR] WSREP: FSM: no such a transition APPLYING -> COMMITTED

      We temporarily switched ALL DB traffic to 10.6.10 node and NO more crash on 10.6.14 node.

      We worry if upgrade the remaining DB node to MariaDB 10.6.14. Both DB nodes will be crashed and cannot be started.

      Kindly advise how to troubleshoot this case.

      Attached the DB parameter file and log of both nodes.




            Unassigned Unassigned
            frelist William Wong
            0 Vote for this issue
            2 Start watching this issue



              Git Integration

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