Comments - mariabackup 10.11.3-MariaDB incremental backup taking long time due to "Waiting for log copy thread to read lsn"
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
SET GLOBAL innodb_log_file_buffering=ON did not help. Also expire_logs_days=3 did not help. I also tried FLUSH LOGS and PURGE LOGS which also does not have an effect. I am wondering why restarting mariadb solves the issue for a couple of days. I noticed that after a restart the time is increasing day by day. Any further ideas what might be the reason for "Waiting for log copy thread to read lsn 11599896005" taking so much time?
Your problem description is very similar to MDEV-31410. You could
SET GLOBAL innodb_max_dirty_pages_pct_lwm=0.001;to make the InnoDB log checkpoint advance more often. This should become unnnecessary once MDEV-30000 has been fixed.To my knowledge,
FLUSH LOGSandPURGE LOGShave nothing to do with the InnoDB storage engine.this seems to have fixed the problem. Thanks a lot for helping. Might there be any negative impact of this setting? Which?