Skip to content

relay: disable WAL recovery logging during subscribe#11755

Merged
locker merged 1 commit intotarantool:masterfrom
locker:relay-disable-wal-recovery-logging
Aug 15, 2025
Merged

relay: disable WAL recovery logging during subscribe#11755
locker merged 1 commit intotarantool:masterfrom
locker:relay-disable-wal-recovery-logging

Conversation

@locker
Copy link
Member

@locker locker commented Aug 14, 2025

If a master instance is under load, it will print hundreds of messages "xxM rows processed" while sending WAL logs to subscribed replicas. This is annoying. These messages are useless because once a replica is subscribed, one can track replication progress through box.info. Let's suppress them.

Closes #11752

If a master instance is under load, it will print hundreds of messages
"xxM rows processed" while sending WAL logs to subscribed replicas.
This is annoying. These messages are useless because once a replica is
subscribed, one can track replication progress through box.info. Let's
suppress them.

Closes tarantool#11752

NO_DOC=bug fix
NO_TEST=logging
@locker locker requested a review from a team as a code owner August 14, 2025 11:14
@locker locker requested review from nshy and sergepetrenko August 14, 2025 11:35
@nshy nshy removed their assignment Aug 14, 2025
Copy link
Collaborator

@sergepetrenko sergepetrenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

@locker locker added the full-ci Enables all tests for a pull request label Aug 15, 2025
@locker locker merged commit d5f5ebe into tarantool:master Aug 15, 2025
57 of 58 checks passed
@locker locker deleted the relay-disable-wal-recovery-logging branch August 15, 2025 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-ci Enables all tests for a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Log spammed with "rows processed" messages with enabled replication under load

4 participants