mirror of
https://git.anonymousland.org/anonymousland/synapse.git
synced 2025-09-25 21:30:53 -04:00
Don't go into federation catch up mode so easily (#9561)
Federation catch up mode is very inefficient if the number of events that the remote server has missed is small, since handling gaps can be very expensive, c.f. #9492. Instead of going into catch up mode whenever we see an error, we instead do so only if we've backed off from trying the remote for more than an hour (the assumption being that in such a case it is more than a transient failure).
This commit is contained in:
parent
af2248f8bf
commit
026503fa3b
5 changed files with 189 additions and 158 deletions
|
@ -7,6 +7,7 @@ from synapse.federation.sender import PerDestinationQueue, TransactionManager
|
|||
from synapse.federation.units import Edu
|
||||
from synapse.rest import admin
|
||||
from synapse.rest.client.v1 import login, room
|
||||
from synapse.util.retryutils import NotRetryingDestination
|
||||
|
||||
from tests.test_utils import event_injection, make_awaitable
|
||||
from tests.unittest import FederatingHomeserverTestCase, override_config
|
||||
|
@ -49,7 +50,7 @@ class FederationCatchUpTestCases(FederatingHomeserverTestCase):
|
|||
else:
|
||||
data = json_cb()
|
||||
self.failed_pdus.extend(data["pdus"])
|
||||
raise IOError("Failed to connect because this is a test!")
|
||||
raise NotRetryingDestination(0, 24 * 60 * 60 * 1000, txn.destination)
|
||||
|
||||
def get_destination_room(self, room: str, destination: str = "host2") -> dict:
|
||||
"""
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue