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

Galera can't perform SST in 10.2.13 if systemd in use due to timeout at startup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 10.1, 10.2.13, 10.2.14, 10.3.6
    • Fix Version/s: N/A
    • Component/s: Configuration
    • Labels:
      None
    • Environment:
      CentOS Linux release 7.4.1708 (Core)

      Description

      The second node can't join the first node because SST will get killed by systemd after the default timeout hits.

      systemctl show mariadb.service | grep Timeout will show timeout set to 1m 30s for startup, but an SST can last hours with large dataset and/or slow disks and/or slow networks.

      In fact, it is common for an SST to take several hours in production.

      Setting TimeoutSec=0 under Services in the mariadb.service config file under systemd fixes the problem.

      Right now, it is impossible to deploy Galera Cluster under 10.2.13 and CentOS 7 unless the above workaround is in place.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jplindst Jan Lindström
              Reporter:
              rpizzi Rick Pizzi
              Votes:
              4 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: