forked from MirrorHub/synapse
3a569fb200
We pull all destinations requiring catchup from the DB in batches. However, if all those destinations get filtered out (due to the federation sender being sharded), then the `last_processed` destination doesn't get updated, and we keep requesting the same set repeatedly.
1 line
114 B
Text
1 line
114 B
Text
Fix bug where sharded federation senders could get stuck repeatedly querying the DB in a loop, using lots of CPU.
|