Terrible tracker scheduling

[donaastor]

On torrents with many trackers, but not so many seeders in average I am experiencing a TERRIBLE tracker scheduling. The first tracker on the list has 0 seeders, 0 leechers and 0 downloaders. Then rtorrent asks that tracker 5 TIMES in a row for seeders. What the f does it expect to happen? There are already 4 FAILED connections, so what could happen in the 5th? Meanwhile, there are 2 other trackers down the list with each having 14 seeders and rtorrent didn't even dare ask them.

Please, add a way to manually ask a tracker for more connections, I am wasting countless minutes waiting for this TERRIBLE scheduler. Please.

[kannibalox]

There are a couple things you could try off the top of my head:

• Go into the "Tracker list" and hit Shift+T a couple times. This should force an announce to happen, which would bump up the failure rate faster than waiting for rTorrent to do it itself.
• Modify the .torrent file to remove this first tracker before loading it
• Use a third party tool to run the t.disable command, e.g. rtxmlrpc t.disable <info hash>:t0