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

Let galera_new_cluster use "restart" instead of "start"

Details

    Description

      The galera_new_cluster command uses "systemctl start" to start up a the initial node of a new galera cluster.

      Unfortunately "systemctl start" does nothing when a service is already started, it just returns success right away. And so does galera_new_cluster then, even though it didn't actually create a new cluster at all.

      So I suggest to change "systemctl start" in the script to "systemctl restart", to enforce a fresh mysqld process start even in cases where the mariadb process is already running.

      Attachments

        Activity

          danblack Daniel Black added a comment -

          Look like a clear 10.3 bug to me.

          danblack Daniel Black added a comment - Look like a clear 10.3 bug to me.

          hholzgra That would mean you can have only one cluster / machine is that intended behavior? (e.g. I have tested 2 cluster cases).

          jplindst Jan Lindström (Inactive) added a comment - hholzgra That would mean you can have only one cluster / machine is that intended behavior? (e.g. I have tested 2 cluster cases).

          For that you can use systemd service templates and pass in a specific name, e.g.

          galera_new_cluster mariadb@node1

          https://mariadb.com/kb/en/getting-started-with-mariadb-galera-cluster/#systemd-and-bootstrapping

          hholzgra Hartmut Holzgraefe added a comment - For that you can use systemd service templates and pass in a specific name, e.g. galera_new_cluster mariadb@node1 https://mariadb.com/kb/en/getting-started-with-mariadb-galera-cluster/#systemd-and-bootstrapping

          People

            jplindst Jan Lindström (Inactive)
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            6 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.