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

MariaDB Crashed when I Updated WSREP_ON Global Variable

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.3.10
    • N/A
    • Galera
    • None
    • RedHat 7.3

    Description

      Today I performed testing on Galera Clustering with MariaDB 10.3.10. I have 3-node cluster.

      I updated the server.cnf with the following statement:

      wsrep_on=OFF

      I restarted mysql by ...

      1. systemctl stop mysql
      1. systemctl sart mysql

      It worked.

      wsrep_cluster_status = Disconnected
       
      MariaDB [(none)]> SHOW global variables  LIKE 'wsrep_on%';
      +---------------+-------+
      | Variable_name | Value |
      +---------------+-------+
      | wsrep_on      | OFF   |
      +---------------+-------+
      

      Then I typed the following command to change wsrep_on to ON:

      MariaDB [(none)]> set global wsrep_on = ON;
       
      MariaDB [(none)]> SHOW global variables  LIKE 'wsrep_on%';
      +---------------+-------+
      | Variable_name | Value |
      +---------------+-------+
      | wsrep_on      | ON    |
      +---------------+-------+
      1 row in set (0.002 sec)
      

      Then, MariaDB was DEAD!

      1. ps -ef|grep mysql
        root 6270 3685 0 17:24 pts/1 00:00:00 grep --color=auto mysql

      Here attached is the error log file.

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            testjetco Test Jetco
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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