[MDEV-17973] Don't overwrite xtrabackup-v2/mariabackup SST logs by default Created: 2018-12-11  Updated: 2020-08-25  Resolved: 2019-01-21

Status: Closed
Project: MariaDB Server
Component/s: Galera, Galera SST, mariabackup
Fix Version/s: 10.4.3, 10.1.38, 10.2.22, 10.3.13

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 2
Labels: galera, mariabackup, sst, syslog, wsrep, xtrabackup

Issue Links:
Relates
relates to MDEV-18372 Minor MDEV-17973-related merge issue ... Closed

 Description   

By default, xtrabackup-v2/mariabackup SSTs log to $datadir/innobackup.backup.log on the donor and $datadir/.sst/innobackup.prepare.log and $datadir/.sst/innobackup.move.log on the joiner. These SST logs are overwritten by each subsequent SST. This makes it very difficult to track down issues with previous SSTs unless you manually save these logs after every SST.

You can enable syslog logging for the SST by setting the following in your MariaDB configuration file:

[sst]
sst-syslog=1

I think the default behavior should be changed, so that diagnostic information about SSTs is not deleted every time.

Maybe syslog logging for the SST should be enabled by default?

Or maybe the SST script should archive old copies of innobackup.backup.log, innobackup.prepare.log, and innobackup.move.log, so that they can be fetched when needed?



 Comments   
Comment by Geoff Montee (Inactive) [ 2019-01-21 ]

I put together a pull request that implements a pretty basic log rotation by default for the mariabackup SST method. What do you think about that idea, jplindst?

Generated at Thu Feb 08 08:40:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.