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

Invalid WSREP_SST rows appear in mysqld-bin.index file

    XMLWordPrintable

    Details

    • Sprint:
      10.1.6-1

      Description

      Invalid rows appear in mysqld-bin.index file, causing server to fail starting. This occurs when WSREP galera replication was enabled. The rows do not point to a valid file but are instead output of wsrep sst.

      Example of contents of mysqld-bin.index:

      mysqld-bin.000001
      ./mysqld-bin.000002
      ./mysqld-bin.000003
      WSREP_SST: [INFO] Preparing binlog files for transfer: (20150224 21:17:07.205)
      mysqld-bin.000004
      ./mysqld-bin.000005
      ./mysqld-bin.000006
      ./mysqld-bin.000007
      WSREP_SST: [INFO] Bypassing state dump. (20150224 21:20:00.648)

      on #maria irc channel was mentioned that:

      "looks like when mariadb forks for a sst it should close all fds for the sst"

        Attachments

        1. cloexec.patch
          2 kB
        2. db1-twice.log
          34 kB
        3. freopen-stdin-devnull.patch
          0.5 kB
        4. mysqld_fd2_usage.scap.gz
          3.02 MB
        5. mysqld_fd2_usage.sysdig.txt.gz
          5.15 MB
        6. repro-galera-invalid-mysqld-bin-index.tar.gz
          4 kB

          Issue Links

            Activity

              People

              Assignee:
              nirbhay_c Nirbhay Choubey (Inactive)
              Reporter:
              rrva Ragnar Rova
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: