[MDEV-7067] Server outputs Galera (WSREP) information, even if Galera is disabled Created: 2014-11-11  Updated: 2015-07-08  Resolved: 2015-05-29

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.1
Fix Version/s: 10.1.5

Type: Bug Priority: Major
Reporter: Tim Callaghan (Inactive) Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 2
Labels: galera

Issue Links:
Duplicate
is duplicated by MDEV-8059 WSREP cause unnecessary messages and ... Closed

 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'



 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2015-04-08 ]

http://lists.askmonty.org/pipermail/commits/2015-April/007729.html

Comment by Nirbhay Choubey (Inactive) [ 2015-04-08 ]

serg Could you please review the patch?

Comment by Nirbhay Choubey (Inactive) [ 2015-05-22 ]

serg Can you please review this updated patch?
http://lists.askmonty.org/pipermail/commits/2015-May/007831.html

Comment by Nirbhay Choubey (Inactive) [ 2015-05-29 ]

http://lists.askmonty.org/pipermail/commits/2015-May/007973.html

Comment by Sergei Golubchik [ 2015-05-29 ]

ok to push

Comment by Nirbhay Choubey (Inactive) [ 2015-05-29 ]

Patch : https://github.com/MariaDB/server/commit/903cfde149778daf67d21144a1172e1ef998599e

Comment by Jean-François Gagné [ 2015-06-11 ]

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
[...]

Comment by Nirbhay Choubey (Inactive) [ 2015-06-11 ]

Hi jgagne!

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!

Comment by Nirbhay Choubey (Inactive) [ 2015-07-08 ]

Hi jgagne!

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.

Generated at Thu Feb 08 07:16:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.