synapse/changelog.d/9770.bugfix
Erik Johnston 3a569fb200 Fix sharded federation sender sometimes using 100% CPU.
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.
2021-04-08 17:34:07 +01:00

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.