mirror of
https://github.com/ppy/osu.git
synced 2024-12-14 08:23:00 +08:00
6ffe8e1713
There are suspicions that the straight 5s retry could have caused a situation a few days ago for `osu-server-spectator` wherein it was getting hammered by constant retry requests. This should make that a little less likely to happen. Numbers chosen are arbitrary, but mostly follow stable's bancho retry intervals because why not. Stable also skips the exponential backoff in case of errors it considers transient, but I decided not to bother for now. Starts off from 3 seconds, then ramps up to up to 2 minutes. Added stagger factor is 25% of duration, either direction. The stagger factor helps given that if spectator server is dead, each client has three separate connections to it which it will retry on (one to each hub). |
||
---|---|---|
.. | ||
API | ||
Chat | ||
Leaderboards | ||
Metadata | ||
Multiplayer | ||
Notifications/WebSocket | ||
Placeholders | ||
Rooms | ||
Solo | ||
Spectator | ||
BeatmapDownloadTracker.cs | ||
DevelopmentEndpointConfiguration.cs | ||
DownloadState.cs | ||
DownloadTracker.cs | ||
EndpointConfiguration.cs | ||
HubClient.cs | ||
HubClientConnector.cs | ||
IHubClientConnector.cs | ||
ILinkHandler.cs | ||
IStatefulUserHubClient.cs | ||
OnlineStatusNotifier.cs | ||
OnlineViewContainer.cs | ||
PersistentEndpointClient.cs | ||
PersistentEndpointClientConnector.cs | ||
PollingComponent.cs | ||
ProductionEndpointConfiguration.cs | ||
ScoreDownloadTracker.cs | ||
SignalRDerivedTypeWorkaroundJsonConverter.cs | ||
SignalRUnionWorkaroundResolver.cs | ||
SignalRWorkaroundTypes.cs |