Opened 13 years ago

Closed 13 years ago

#1045 closed Bug (fixed)

Rescraping every 0 seconds

Reported by: Waldorf Owned by: charles
Priority: Normal Milestone: 1.30
Component: libtransmission Version: 1.22
Severity: Normal Keywords:
Cc:

Description

From IRC:

joneskoo: is there a reason why Transmission would rescrape constantly one paused torrent?
joneskoo: I watched message log with filter Error
joneskoo: I see messages like this
joneskoo: Scrape successful. Rescraping in 0 seconds.
joneskoo: request succeeded. rescraping in 0 seconds
preaction: looks like a bug, maybe the tracker isn't sending back an interval (though i didn't
           know that was part of the scrape protocol)
joneskoo: I removed the torrent from the list to avoid killing the tracker
joneskoo: one other paused seed has "rescraping in 0 seconds" / "rescraping in 4 seconds"
          and it appears to scrape every 4 seconds
joneskoo: I think 4 seconds is still quite fast and loads the tracker unnecessarily,
          don't you think?

Change History (3)

comment:1 Changed 13 years ago by livings124

Could you point us towards a torrent that produces this behavior?

comment:2 Changed 13 years ago by charles

  • Milestone changed from None Set to 1.30
  • Status changed from new to assigned
  • Version changed from 1.22+ to 1.22

Changing the version from 1.22+ to 1.22 because this isn't new behavior in the development builds...

comment:3 Changed 13 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

The only place that the `0' in that message can come from, is assigned directly from the tracker. It looks like the tracker is returning a min_announce_interval of zero. Alternatively, it may be sending back malformed benc data. (This is less likely, since our benc parser has a few sanity checks that should've complained before the error message being reported here).

Either way, we should gracefully handle the situation where the tracker gives us a scrape interval that's lower than we actually want. Fixed in r6281.

Note: See TracTickets for help on using tickets.