diff options
| author | Erik Johnston <erik@matrix.org> | 2022-05-05 10:20:23 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-05 10:20:23 +0100 |
| commit | c0379d6e5b3ec277788018670e69f9dc848bfb34 (patch) | |
| tree | 2d5a8664c03b0087ee61aa15cdd8c09f7cebff07 /synapse/replication/tcp/resource.py | |
| parent | Add `mau_appservice_trial_days` config (#12619) (diff) | |
| download | synapse-c0379d6e5b3ec277788018670e69f9dc848bfb34.tar.xz | |
Reduce log spam when running multiple event persisters (#12610)
Diffstat (limited to '')
| -rw-r--r-- | synapse/replication/tcp/resource.py | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/synapse/replication/tcp/resource.py b/synapse/replication/tcp/resource.py index c6870df8f9..99f09669f0 100644 --- a/synapse/replication/tcp/resource.py +++ b/synapse/replication/tcp/resource.py @@ -204,6 +204,15 @@ class ReplicationStreamer: # turns out that e.g. account data streams share # their "current token" with each other, meaning # that it is *not* safe to send a POSITION. + + # Note: `last_token` may not *actually* be the + # last token we sent out in a RDATA or POSITION. + # This can happen if we sent out an RDATA for + # position X when our current token was say X+1. + # Other workers will see RDATA for X and then a + # POSITION with last token of X+1, which will + # cause them to check if there were any missing + # updates between X and X+1. logger.info( "Sending position: %s -> %s", stream.NAME, |