Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#2388 closed Bug (fixed)

dead trackers can logjam up the announce & scrape queue

Reported by: charles Owned by: charles
Priority: Normal Milestone: 1.75
Component: libtransmission Version: 1.74
Severity: Major Keywords: backport-1.5x


In 1.74, Transmission waits a full two minutes before timing out an announce request to the tracker, and 30 seconds for scrapes. If you have a lot of torrents on the same tracker, it's very easy for a single unresponsive tracker to tie up all the "active" slots in Transmission's announce & scrape queue.

In the short term (1.75) we should reduce the timeout period for announces & scrapes. Bad trackers will still be able to tie up the active slots, but this way they won't be able to do it for as long. This only requires a couple of one-line changes and is less risky for a bugfix release.

For 1.80, we should recognize unresponsive trackers and de-prioritize them s.t. other trackers go ahead of them in the queue, as well as the existing request to handle the tiers in parallel rather than in serial. (The latter is ticket #1699).

Change History (4)

comment:1 Changed 13 years ago by charles

  • Severity changed from Normal to Major
  • Status changed from new to assigned

comment:2 Changed 13 years ago by charles

short-term goal of reducing the timeout period for announces & scrapes: fixed in 1.7x by r9058 for 1.75 fixed in trunk by r9069 for 1.80

comment:3 Changed 13 years ago by charles

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

comment:4 Changed 13 years ago by charles

  • Keywords backport-1.5x added
Note: See TracTickets for help on using tickets.