[MDEV-7891] Don't write meaningless WSREP messages to stdout / error log Created: 2015-03-31  Updated: 2015-04-08  Resolved: 2015-04-08

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 10.1.3
Fix Version/s: 10.1.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Nirbhay Choubey (Inactive)
Resolution: Duplicate Votes: 0
Labels: None


 Description   

The script writes it every time when it gets started, even though it has no wsrep/galera configuration whatsoever. Please don't do it. 

150331 15:45:27 mysqld_safe WSREP: Running position recovery with --log_error='/data/releases/mariadb-10.1.3-linux-x86_64/data/wsrep_recovery.dlREN7' --pid-file='/data/releases/mariadb-10.1.3-linux-x86_64/data/wheezy-64-recover.pid'
 
150331 15:45:30 mysqld_safe WSREP: Position recovery skipped

It's useless noise for a standalone server.
Please don't write "Running position recovery" if it is "skipped" anyway; and try not to write "skipped" either, unless it's skipped on a questionable reason.



 Comments   
Comment by Sergei Golubchik [ 2015-03-31 ]

I would generally prefer wsrep to be much less visible in 10.1+. Like, not add wsrep to the server version, etc. It made sense when we had a special "wsrep-patched" server version. But when wsrep is always in the server, it's kind of redundant to mark the server as "contains wsrep"

Comment by Elena Stepanova [ 2015-03-31 ]

That's right, I also vote for removing it from the version.

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

Duplicate of MDEV-7067

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