Only 1 tracker works at a time

[absolutep]

Only one tracker works at a time, despite of Tribler having facility to add more than one tracker.

I tried to force recheck them but that facility [force recheck] does not work at all.

tribler 8.0.5.x64
windows 10

[qstokkink]

This is working as intended. According to the official BitTorrent protocol specification, BEP0012 in this case, after a working tracker is selected no other trackers are used. The others are considered "backup" trackers and neglected. This behavior is even enforced and tested in our core torrent library.

I double-checked the force recheck button and it appears to be correctly force-rechecking. However, force-rechecking a "Not working" tracker normally does not magically make it "Working".

We can try to see if we can "massage" our core torrent library a bit to make it check all trackers anyway. However, I can't guarantee that it will allow us to add this.

[absolutep]

This is working as intended. According to the official BitTorrent protocol specification, BEP0012 in this case, after a working tracker is selected no other trackers are used. The others are considered "backup" trackers and neglected. This behavior is even enforced and tested in our core torrent library.

Oh! Okay!

I did not know that. Thanks for telling me.

If it chooses a backup tracker automatically, in case of a failure of the initially selected one, and then renounces the new tracker automatically without the need of manual intervention, then everything is fine by me.

Thanks.

[absolutep]

Re-opening it because it is not working as intended.
Heavily in-demand recent torrent.

[qstokkink]

From my tests, "Not working" trackers are only marked as such if they really do not respond after the timeout. Tribler doesn't seem to be at fault here. HOWEVER, assuming that these trackers are reachable, this could be a bug in our inner libtorrent upstream dependency.

To confirm, we would have to manually contact the trackers and see if they are really unreachable or if the libtorrent library is incorrectly contacting them (or if the combination of technologies is causing some complex failure).

[teddyrogers]

Scenario Tribler announces to a tracker with zero peers whilst another tracker has hundreds. Would it be better to announce to all trackers and check for and connect to peers?