high enough tracker errors cause all trackers to fail

[rezad1393]

I have about 1200 torrent in rtorrent.
about 300 of them are from a tracker that has connection issues.
when I run those torrent and they get timeout error after some short time all of torrents (not just the that specific tracker) timeout.
all of them..

[kannibalox]

What's probably happening is that the tracker with the connection issues is causing sockets/HTTP calls to queue up, blocking calls that would otherwise succeed quickly. The simplest solution is to just disable the tracker that's causing issues, otherwise you can look into increasing the limits of network.http.max_open.set or network.max_open_sockets.set. See https://github.com/rakshasa/rtorrent/wiki/Performance-Tuning#system-wide-settings for general performance tuning.

[rezad1393]

this doesnt happen with transmission torrent client (I think)

maybe a interval should be used before trying timeouted trackers (which I think rtorrent has) and remove the buggy http from http queue unitl next interval (which it seems rtorrent doesnt)

just removing a tracker would not be the solution as rotternt is used for many seedoxes that are set up and left to run and this would cause the seeding to stop for all trackers even with one tracker failing.

[rakshasa]

Are those udp trackers?

[rezad1393]

Are those udp trackers?

no.
they are all private http trackers.

[rakshasa]

I've started working on making trackers multithreaded, however it's going to take some time. Will have to revisit this issue when that is done.

[rezad1393]

I've started working on making trackers multithreaded, however it's going to take some time. Will have to revisit this issue when that is done.

thank you.
I think torrent client in general are not really multi-thread optimized.
for example checking file after completion almost make rtorrent die.
or even moving multiple torrents from a folder to another.