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

socat dependency for sst in 10.1+

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.1.23, 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
    • N/A
    • Galera SST
    • None

    Description

      The problem was fixed for pre-10.1 in MDEV-7233, but it re-appear after moving galera inside server.

      So, here is typical the pattern:

      • rsync - sst method is used in Galera
      • Server is upgraded to new version with mariabackup
      • mariabackup (or xtrabackup) is evaluated and is confirmed to work properly for basic backup/restore operations on single node
      • sst configuration is changed to mariabackup (or xtrabackup-v2)
      • error is observed in logs during sst 'socat is not found in path' when new sst method is used

      We shall break this pattern somehow if possible

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-13993 Transition from 'net-tools' to 'iproute2'

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-7233 Fix issue with missing dependency socat when installing MariaDB-galera-server on RedhatEL/OracleEL/(Others?) RPM based

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15638 galera package should contain dependecy on socat

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            serg Sergei Golubchik added a comment -

            From technical point of view: even if we can deploy that in new my.cnf - are we are capable of injecting that line into existing configuration files (which sometimes even may be generated by third party).

            No, of course, not. What I mean is merely

            --- a/support-files/wsrep.cnf.sh
            		 
            +++ b/support-files/wsrep.cnf.sh
            		 
            @@ -101,6 +101,8 @@ wsrep_notify_cmd=
            		 
             ##
            		 
             
             # State Snapshot Transfer method
            		 
            +# Allowed values are rsync, xtrabackup-v2, mariabackup, mysqldump
            		 
            +# when using mariabackup or xtrabackup-v2, make sure you have socat installed
            		 
             wsrep_sst_method=rsync
            		 
             
             # Address which donor should send State Snapshot to.

            And, of course, I agree that this should be documented in KB.

            serg Sergei Golubchik added a comment - From technical point of view: even if we can deploy that in new my.cnf - are we are capable of injecting that line into existing configuration files (which sometimes even may be generated by third party). No, of course, not. What I mean is merely --- a/support-files/wsrep.cnf.sh +++ b/support-files/wsrep.cnf.sh @@ -101,6 +101,8 @@ wsrep_notify_cmd= ## # State Snapshot Transfer method +# Allowed values are rsync, xtrabackup-v2, mariabackup, mysqldump +# when using mariabackup or xtrabackup-v2, make sure you have socat installed wsrep_sst_method=rsync # Address which donor should send State Snapshot to. And, of course, I agree that this should be documented in KB.
            sysprg Julius Goryavsky added a comment -

            jplindst I think we can just close this, because all the necessary checks and intelligible diagnostics have long been added to all versions.

            sysprg Julius Goryavsky added a comment - jplindst I think we can just close this, because all the necessary checks and intelligible diagnostics have long been added to all versions.
            jplindst Jan Lindström (Inactive) added a comment -

            We cannot add hard requirement of socat dependency on GA-releases. I do not exactly know but maybe you could add it as "suggest" on upgrade.

            jplindst Jan Lindström (Inactive) added a comment - We cannot add hard requirement of socat dependency on GA-releases. I do not exactly know but maybe you could add it as "suggest" on upgrade.
            serg Sergei Golubchik added a comment -

            There is nothing in the server package that requires socat. The server doesn't, none of the tools does, none of the scripts does, even wsrep_sst_mariabackup doesn't, it can use nc.

            serg Sergei Golubchik added a comment - There is nothing in the server package that requires socat. The server doesn't, none of the tools does, none of the scripts does, even wsrep_sst_mariabackup doesn't, it can use nc .
            valerii Valerii Kravchuk added a comment -

            Doesn't this line (https://github.com/MariaDB/server/blob/3bf42eb21bb8744b12b2b5ddb4f87425e328c36f/scripts/wsrep_sst_mariabackup.sh#L481):

            tfmt=$(parse_cnf sst transferfmt 'socat')

            mean that socat is used by default (inherited from https://www.percona.com/doc/percona-xtradb-cluster/LATEST/manual/xtrabackup_sst.html#transferfmt)? DBA sets nothing explicit bug SST method and ends up with the need for socat

            Also what about this KB article, https://mariadb.com/kb/en/mariabackup-sst-method/:

            "Note that if you use the mariabackup SST method, then you also need to have socat installed on the server. This is needed to stream the backup from the donor node to the joiner node. This is a limitation that was inherited from the xtrabackup-v2 SST method."

            So, unless we change default transer format to nc, socat is mandatory for mariabackup SST method (that itself is the de-facto default one for production use).

            valerii Valerii Kravchuk added a comment - Doesn't this line ( https://github.com/MariaDB/server/blob/3bf42eb21bb8744b12b2b5ddb4f87425e328c36f/scripts/wsrep_sst_mariabackup.sh#L481): tfmt=$(parse_cnf sst transferfmt 'socat') mean that socat is used by default (inherited from https://www.percona.com/doc/percona-xtradb-cluster/LATEST/manual/xtrabackup_sst.html#transferfmt)? DBA sets nothing explicit bug SST method and ends up with the need for socat Also what about this KB article, https://mariadb.com/kb/en/mariabackup-sst-method/: "Note that if you use the mariabackup SST method, then you also need to have socat installed on the server. This is needed to stream the backup from the donor node to the joiner node. This is a limitation that was inherited from the xtrabackup-v2 SST method." So, unless we change default transer format to nc, socat is mandatory for mariabackup SST method (that itself is the de-facto default one for production use).

            People

              jplindst Jan Lindström (Inactive)
              anikitin Andrii Nikitin (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 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.