Changeset 10034

Timestamp:

Jan 28, 2010, 7:33:48 PM (12 years ago)

Author:

charles

Message:

(trunk libT) if a tracker doesn't respond during an announce, instead of automatically reannouncing in 120 seconds, add some fuzz to the interval. Rationale: if a bunch of torrents announce at once, overloading the router or server, they'll still be overloading it if we do the exact same thing the second time around...

File:

• trunk/libtransmission/announcer.c (modified) (1 diff)

trunk/libtransmission/announcer.c

@@ -1265 +1265 @@
         if( responseCode == 0 )
         {
-            dbgmsg( tier, "No response from tracker... retrying in two minutes." );
+            const int interval = 120 + tr_cryptoWeakRandInt( 120 );
+            dbgmsg( tier, "No response from tracker... retrying in %d seconds.", interval );
             tier->manualAnnounceAllowedAt = ~(time_t)0;
-            tierSetNextAnnounce( tier, tier->announceEvent, now + 120 );
+            tierSetNextAnnounce( tier, tier->announceEvent, now + interval );
         }
         else if( 200 <= responseCode && responseCode <= 299 )