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

Server outputs Galera (WSREP) information, even if Galera is disabled

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.1
    • Fix Version/s: 10.1.5
    • Component/s: Galera
    • Labels:

      Description

      Downloaded MariaDB 10.1.1 tarball, unpacked and initialized database, started MariaDB. Left all wsrep server variables at defaults.

      Server is reporting WSREP information even though Galera is disabled by default, which is confusing.

      — banner —
      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 2
      Server version: 10.1.1-MariaDB-wsrep MariaDB Server, wsrep_25.10.r4123
      
      — initialization —
      141111  8:54:49 [Note] WSREP: Read nil XID from storage engines, skipping position init
      141111  8:54:49 [Note] WSREP: wsrep_load(): loading provider library 'none'
      141111  8:54:49 [Note] WSREP: Service disconnected.
      141111  8:54:50 [Note] WSREP: Some threads may fail to exit.
      
      — server log on startup —
      141111 08:54:53 mysqld_safe WSREP: Running position recovery with --log_error='/home/tcallaghan/data/dbtest/mariadb-10.1.1-linux-x86_64/data/wsrep_recovery.VChH7B' --pid-file='/home/tcallaghan/data/dbtest/mariadb-10.1.1-linux-x86_64/data/tmc-recover.pid'
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Show
              nirbhay_c Nirbhay Choubey added a comment - http://lists.askmonty.org/pipermail/commits/2015-April/007729.html
              Hide
              nirbhay_c Nirbhay Choubey added a comment -

              Sergei Golubchik Could you please review the patch?

              Show
              nirbhay_c Nirbhay Choubey added a comment - Sergei Golubchik Could you please review the patch?
              Hide
              nirbhay_c Nirbhay Choubey added a comment -
              Show
              nirbhay_c Nirbhay Choubey added a comment - Sergei Golubchik Can you please review this updated patch? http://lists.askmonty.org/pipermail/commits/2015-May/007831.html
              Show
              nirbhay_c Nirbhay Choubey added a comment - http://lists.askmonty.org/pipermail/commits/2015-May/007973.html
              Hide
              serg Sergei Golubchik added a comment -

              ok to push

              Show
              serg Sergei Golubchik added a comment - ok to push
              Show
              nirbhay_c Nirbhay Choubey added a comment - Patch : https://github.com/MariaDB/server/commit/903cfde149778daf67d21144a1172e1ef998599e
              Hide
              jgagne Jean-François Gagné added a comment -

              Still some WSREP in 10.1.5. On startup:

              [...]
              2015-06-10 13:47:03 140177671497760 [Note] /usr/sbin/mysqld (mysqld 10.1.5-MariaDB-log) starting as process 60572 ...
              [...]
              2015-06-10 13:47:17 140177671497760 [Note] WSREP: Read nil XID from storage engines, skipping position init
              2015-06-10 13:47:17 140177671497760 [Note] WSREP: wsrep_load(): loading provider library 'none'
              [...]

              On shutdown:

              2015-06-10 15:14:41 140177669834496 [Note] /usr/sbin/mysqld: Normal shutdown
              2015-06-10 15:14:41 140177669834496 [Note] WSREP: Stop replication
              [...]

              Show
              jgagne Jean-François Gagné added a comment - Still some WSREP in 10.1.5. On startup: [...] 2015-06-10 13:47:03 140177671497760 [Note] /usr/sbin/mysqld (mysqld 10.1.5-MariaDB-log) starting as process 60572 ... [...] 2015-06-10 13:47:17 140177671497760 [Note] WSREP: Read nil XID from storage engines, skipping position init 2015-06-10 13:47:17 140177671497760 [Note] WSREP: wsrep_load(): loading provider library 'none' [...] On shutdown: 2015-06-10 15:14:41 140177669834496 [Note] /usr/sbin/mysqld: Normal shutdown 2015-06-10 15:14:41 140177669834496 [Note] WSREP: Stop replication [...]
              Hide
              nirbhay_c Nirbhay Choubey added a comment -

              Hi Jean-François Gagné!

              As cluster configurations are mostly dynamic, a dummy wsrep loaded in needed to fill-in.
              However, the dummy loader itself consists of a set of empty stubs, so, its effect should
              be insignificant.
              On shutdown, we explicitly need to check and stop wsrep replication threads, again,
              because cluster configs are dynamic. (Refer: MDEV-7798).

              Thanks!

              Show
              nirbhay_c Nirbhay Choubey added a comment - Hi Jean-François Gagné ! As cluster configurations are mostly dynamic, a dummy wsrep loaded in needed to fill-in. However, the dummy loader itself consists of a set of empty stubs, so, its effect should be insignificant. On shutdown, we explicitly need to check and stop wsrep replication threads, again, because cluster configs are dynamic. (Refer: MDEV-7798 ). Thanks!
              Hide
              nirbhay_c Nirbhay Choubey added a comment -

              Hi Jean-François Gagné!

              I have pushed the following changes to remove wsrep-related stuff if sever
              is started without wsrep enabled.

              https://github.com/MariaDB/server/commit/8154ef4b16fe140a42f3e90903192bb3b0fec041.patch

              Thanks for reporting.

              Show
              nirbhay_c Nirbhay Choubey added a comment - Hi Jean-François Gagné ! I have pushed the following changes to remove wsrep-related stuff if sever is started without wsrep enabled. https://github.com/MariaDB/server/commit/8154ef4b16fe140a42f3e90903192bb3b0fec041.patch Thanks for reporting.

                People

                • Assignee:
                  nirbhay_c Nirbhay Choubey
                  Reporter:
                  tmcallaghan Tim Callaghan
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 40 minutes
                    40m