mirror of
https://github.com/transmission/transmission
synced 2024-12-27 18:18:10 +00:00
(trunk libT) use get_next_scrape_time() inside the scrape error handler.
get_next_scrape_time() was introduced in r12297. The rationale is that by rounding all scrape times to their nearest 10th second, they will tend to occur in batches and improve multiscrape.
This commit is contained in:
parent
4a5415e84c
commit
35eb016209
1 changed files with 1 additions and 1 deletions
|
@ -1183,7 +1183,7 @@ on_scrape_error( tr_tier * tier, const char * errmsg )
|
||||||
tierIncrementTracker( tier );
|
tierIncrementTracker( tier );
|
||||||
|
|
||||||
/* schedule a rescrape */
|
/* schedule a rescrape */
|
||||||
interval = getRetryInterval( tier->currentTracker );
|
interval = get_next_scrape_time( getRetryInterval( tier->currentTracker ) );
|
||||||
dbgmsg( tier, "Retrying scrape in %d seconds.", interval );
|
dbgmsg( tier, "Retrying scrape in %d seconds.", interval );
|
||||||
tr_torinf( tier->tor, "Retrying scrape in %d seconds.", interval );
|
tr_torinf( tier->tor, "Retrying scrape in %d seconds.", interval );
|
||||||
tier->lastScrapeSucceeded = false;
|
tier->lastScrapeSucceeded = false;
|
||||||
|
|
Loading…
Reference in a new issue